From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: jeff@garzik.org
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [E1000-devel] [PATCH 4/8] e1000e: lower ring minimum size to 64
Date: Wed, 23 Apr 2008 11:12:46 -0700 [thread overview]
Message-ID: <480F7C1E.4090900@intel.com> (raw)
In-Reply-To: <20080423180919.24972.67080.stgit@localhost.localdomain>
Auke Kok wrote:
> The lower limit of 80 descriptors in the ring is only valid for
> one older 8254x chipset. All e1000e devices can use as low as
> 64 descriptors.
>
> Signed-off-by: Auke Kok <auke-jan.h.kok@intel.com>
Jeff,
patch #1-4 are RESENDS, where I omitted the VLAN/TSO fix that PJ will respin.
patch 5-8 are trivial patches (partial RESENDS) that I did not see merged yet and
I could not find in any of your trees ATM. apologies if I sound pushy - just
making sure these don't fall through the cracks ;)
Cheers
Auke
next prev parent reply other threads:[~2008-04-23 18:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 18:09 [PATCH 1/8] e1000e: cleanup several stats issues Auke Kok
2008-04-23 18:09 ` [PATCH 2/8] e1000e: Add interrupt moderation run-time ethtool interface Auke Kok
2008-04-23 18:09 ` [PATCH 3/8] e1000e: Fix HW Error on es2lan, ARP capture issue by BMC Auke Kok
2008-04-23 18:09 ` [PATCH 4/8] e1000e: lower ring minimum size to 64 Auke Kok
2008-04-23 18:12 ` Kok, Auke [this message]
2008-04-23 18:09 ` [PATCH 5/8] ixgbe: save and restore pcie/msi state to support EEH recovery Auke Kok
2008-04-23 18:09 ` [PATCH 6/8] e1000e: " Auke Kok
2008-04-23 18:09 ` [PATCH 7/8] [RESEND] igb: " Auke Kok
2008-04-23 18:09 ` [PATCH 8/8] e1000e: Increment version to 0.2.1 Auke Kok
2008-04-25 6:01 ` [PATCH 1/8] e1000e: cleanup several stats issues Jeff Garzik
2008-04-25 16:39 ` Kok, Auke
2008-04-28 22:13 ` Kok, Auke
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=480F7C1E.4090900@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeff@garzik.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).