From: Ron Mercer <ron.mercer@qlogic.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, ron.mercer@qlogic.com
Subject: [net-next PATCH 0/3] qlge: Performance changes for qlge.
Date: Sat, 2 Jan 2010 12:37:41 -0800 [thread overview]
Message-ID: <1262464664-14996-1-git-send-email-ron.mercer@qlogic.com> (raw)
Currently qlge splits headers into a separate buffer so they can
be re-aligned on a 2-byte boundary. This is done to avoid
exceptions thrown on certain platforms when headers are processed.
To avoid the overhead of re-aligning headers, we turn on the split
header/realign configuration only when the platform requires it.
This allows usage of the gro-frags interface on platforms that do
not require 32 bit aligned headers.
next reply other threads:[~2010-01-02 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 20:37 Ron Mercer [this message]
2010-01-02 20:37 ` [net-next PATCH 1/3] qlge: Turn on RX header split based on platform Ron Mercer
2010-01-02 20:37 ` [net-next PATCH 2/3] qlge: Add RX frame handlers for non-split frames Ron Mercer
2010-01-02 20:37 ` [net-next PATCH 3/3] qlge: Add napi gro frags interface Ron Mercer
2010-01-07 4:30 ` [net-next PATCH 0/3] qlge: Performance changes for qlge 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=1262464664-14996-1-git-send-email-ron.mercer@qlogic.com \
--to=ron.mercer@qlogic.com \
--cc=davem@davemloft.net \
--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).