From: Ben Hutchings <bhutchings@solarflare.com>
To: Jesse Gross <jesse@nicira.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] offloading: Make scatter/gather more tolerant of vlans.
Date: Mon, 01 Nov 2010 20:06:29 +0000 [thread overview]
Message-ID: <1288641989.2231.3.camel@achroite.uk.solarflarecom.com> (raw)
In-Reply-To: <1288390495-28923-1-git-send-email-jesse@nicira.com>
On Fri, 2010-10-29 at 15:14 -0700, Jesse Gross wrote:
> When checking if it is necessary to linearize a packet, we currently
> use vlan_features if the packet contains either an in-band or out-
> of-band vlan tag. However, in-band tags aren't special in any way
> for scatter/gather since they are part of the packet buffer and are
> simply more data to DMA. Therefore, only use vlan_features for out-
> of-band tags, which could potentially have some interaction with
> scatter/gather.
>
> Signed-off-by: Jesse Gross <jesse@nicira.com>
> CC: Ben Hutchings <bhutchings@solarflare.com>
[...]
Reviewed-by: Ben Hutchings <bhutchings@solarflare.com>
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-11-01 20:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 22:14 [PATCH 1/3] offloading: Make scatter/gather more tolerant of vlans Jesse Gross
2010-10-29 22:14 ` [PATCH 2/3] offloading: Support multiple vlan tags in GSO Jesse Gross
2010-11-01 20:33 ` Ben Hutchings
2010-11-02 1:31 ` Jesse Gross
2010-11-15 17:23 ` David Miller
2010-10-29 22:14 ` [PATCH 3/3] offloading: Force software GSO for multiple vlan tags Jesse Gross
2010-11-15 17:23 ` David Miller
2011-01-07 19:36 ` Michał Mirosław
2011-01-09 16:00 ` Jesse Gross
2010-11-01 20:06 ` Ben Hutchings [this message]
2010-11-15 17:23 ` [PATCH 1/3] offloading: Make scatter/gather more tolerant of vlans David Miller
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=1288641989.2231.3.camel@achroite.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.