From: Andrew Gallatin <gallatin@myri•com>
To: David Miller <davem@davemloft•net>
Cc: eric.dumazet@gmail•com, bhutchings@solarflare•com,
netdev@vger•kernel.org, linux-net-drivers@solarflare•com,
herbert@gondor•hengli.com.au
Subject: Re: [PATCH net-next] gro: Handle inline VLAN tags
Date: Wed, 28 Nov 2012 12:30:12 -0500 [thread overview]
Message-ID: <50B64A24.60200@myri.com> (raw)
In-Reply-To: <20121128.114602.1208211617672057364.davem@davemloft.net>
On 11/28/12 11:46, David Miller wrote:
> From: Andrew Gallatin <gallatin@myri•com>
> Date: Mon, 26 Nov 2012 10:04:44 -0500
>
>> How do you feel about the patchset I posted on 11/14/2012
>> ([PATCH net-next 0/3] myri10ge: LRO to GRO conversion,
>> http://marc.info/?l=linux-netdev&m=135289838223920&w=2)
>> which moves myri10ge from LRO to GRO?
>>
>> Specifically, if doing vlan decap in GRO is not OK, then how
>> about doing it in the driver?
>
> I'm going to trust Eric's judgment on this one, as he has been
> thinking more about the long term GRO issues than I have.
>
> Thanks.
>
Perfect, thanks. Eric seemed OK with doing the vlan decap
in the driver. But.. I didn't get an "nack" or an "applied" from
you in response to that myri10ge patchset. Do I need to re-submit it?
Sorry, I'm not terribly familiar with the etiquette for this sort
of thing.
Thanks,
Drew
next prev parent reply other threads:[~2012-11-28 17:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 20:17 [PATCH net-next] gro: Handle inline VLAN tags Ben Hutchings
2012-11-16 23:01 ` Eric Dumazet
2012-11-17 0:00 ` Ben Hutchings
2012-11-17 0:16 ` Eric Dumazet
2012-11-17 0:32 ` Ben Hutchings
2012-11-17 1:09 ` Eric Dumazet
2012-11-20 0:10 ` David Miller
2012-11-26 15:04 ` Andrew Gallatin
2012-11-28 16:46 ` David Miller
2012-11-28 17:30 ` Andrew Gallatin [this message]
2012-11-28 18:39 ` David Miller
2012-11-17 1:17 ` Andrew Gallatin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50B64A24.60200@myri.com \
--to=gallatin@myri$(echo .)com \
--cc=bhutchings@solarflare$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=herbert@gondor$(echo .)hengli.com.au \
--cc=linux-net-drivers@solarflare$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox