From: Rick Jones <rick.jones2@hp.com>
To: Divy Le Ray <divy@chelsio.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, swise@opengridcomputing.com,
leedom@chelsio.com
Subject: Re: [PATCH 2.6.28] cxgb3 - Fix LRO misalignment
Date: Thu, 15 Jan 2009 17:57:07 -0800 [thread overview]
Message-ID: <496FE973.1060106@hp.com> (raw)
In-Reply-To: <20090116004829.7437.52798.stgit@speedy5>
Divy Le Ray wrote:
> From: Divy Le Ray <divy@chelsio.com>
>
> The lro manager's frag_align_pad setting was missing,
> leading to misaligned access to the skb passed up
> to the stack.
>
> Signed-off-by: Divy Le Ray <divy@chelsio.com>
I have tried this in a tree I have, and where I was once seeing unaligned access
messages on an ia64 system with LRO enabled, now I see none.
Tested-by: Rick Jones <rick.jones2@hp.com>
rick jones
next prev parent reply other threads:[~2009-01-16 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 0:48 [PATCH 2.6.28] cxgb3 - Fix LRO misalignment Divy Le Ray
2009-01-16 1:57 ` Rick Jones [this message]
2009-01-16 19:05 ` Divy Le Ray
2009-01-19 6:01 ` 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=496FE973.1060106@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=divy@chelsio.com \
--cc=leedom@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=swise@opengridcomputing.com \
/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).