From: David Miller <davem@davemloft.net>
To: ecashin@coraid.com
Cc: akpm@linux-foundation.org, bhutchings@solarflare.com,
jesse@nicira.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] do not disable sg when packet requires no checksum
Date: Thu, 20 Sep 2012 22:32:37 -0400 (EDT) [thread overview]
Message-ID: <20120920.223237.770883586764737313.davem@davemloft.net> (raw)
In-Reply-To: <cover.1348105262.git.ecashin@coraid.com>
From: Ed Cashin <ecashin@coraid.com>
Date: Wed, 19 Sep 2012 18:46:07 -0700
> This two-part patchset replaces an earlier net-only patch that
> added an explicit check for the AoE protocol to harmonize_features
> in net/core/dev.c.
>
> Following the suggestions of Ben Hutchings, this patchset makes
> the decision in the network layer protocol agnostic instead of
> using ETH_P_AOE as a special case. It relies on fresh skbs being
> CHECKSUM_NONE but makes that explicit with an assertion.
>
> Ed L. Cashin (2):
> aoe: assert AoE packets marked as requiring no checksum
> net: do not disable sg for packets requiring no checksum
Applied and queued up for -stable, thanks Ed.
next prev parent reply other threads:[~2012-09-21 2:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 1:46 [PATCH 0/2] do not disable sg when packet requires no checksum Ed Cashin
2012-09-20 1:46 ` [PATCH 1/2] aoe: assert AoE packets marked as requiring " Ed Cashin
2012-09-20 1:49 ` [PATCH 2/2] net: do not disable sg for packets " Ed Cashin
2012-09-21 2:32 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-19 0:20 [PATCH] net: do not disable sg for AoE Ed Cashin
2012-09-19 19:55 ` Ben Hutchings
2012-09-20 1:16 ` [PATCH 0/2] do not disable sg when packet requires no checksum Ed Cashin
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=20120920.223237.770883586764737313.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=bhutchings@solarflare.com \
--cc=ecashin@coraid.com \
--cc=jesse@nicira.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).