From: Rick Jones <rick.jones2@hp.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: eilong@broadcom.com, David Miller <davem@davemloft.net>,
"ole@ans.pl" <ole@ans.pl>,
"eric.dumazet@gmail.com" <eric.dumazet@gmail.com>
Subject: Re: [RFC] bnx2x: Insane RX rings
Date: Fri, 10 Sep 2010 08:54:08 -0700 [thread overview]
Message-ID: <4C8A54A0.4030907@hp.com> (raw)
In-Reply-To: <4C8A52BE.9040105@hp.com>
> At one level we are talking about horses and barn doors - for example,
> the minimum memory requirements for ProLiants have already been set (and
> communicated for some time) taking memory usage of their LOMs (Lan On
> Motherboard) into account.
Their 10GbE LOMs that is...just to state the implicitly obvious.
rick
next prev parent reply other threads:[~2010-09-10 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 20:45 [RFC] bnx2x: Insane RX rings Eric Dumazet
2010-09-09 21:21 ` Krzysztof Olędzki
2010-09-09 21:30 ` David Miller
2010-09-09 21:38 ` Rick Jones
2010-09-10 11:16 ` Eilon Greenstein
2010-09-10 15:46 ` Rick Jones
2010-09-10 15:54 ` Rick Jones [this message]
2010-09-10 16:42 ` 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=4C8A54A0.4030907@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ole@ans.pl \
/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).