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: Size RX buffers based on MTU.
Date: Fri, 16 Oct 2009 13:15:33 -0700 [thread overview]
Message-ID: <1255724136-27264-1-git-send-email-ron.mercer@qlogic.com> (raw)
Change RX large buffer size based on MTU. If pages are larger
than the MTU the page is divided up into multiple chunks and passed to
the hardware. When pages are smaller than MTU each RX buffer can
contain be comprised of up to 2 pages.
Dave,
These patches are interdependent.
next reply other threads:[~2009-10-16 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 20:15 Ron Mercer [this message]
2009-10-16 20:15 ` [net-next PATCH 1/3] qlge: Size RX buffers based on MTU (header changes) Ron Mercer
2009-10-16 20:15 ` [net-next PATCH 2/3] qlge: Size RX buffers based on MTU (Add API) Ron Mercer
2009-10-16 20:15 ` [net-next PATCH 3/3] qlge: Size RX buffers based on MTU changes Ron Mercer
2009-10-17 0:51 ` [net-next PATCH 0/3] qlge: Size RX buffers based on MTU David Miller
2009-10-17 2:22 ` Ron Mercer
2009-10-17 22:37 ` David Miller
2009-10-19 13:29 ` Ron Mercer
2009-10-19 13:32 ` [net-next PATCH 1/1] " Ron Mercer
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=1255724136-27264-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