From: Rick Jones <rick.jones2@hp.com>
To: netdev@oss.sgi.com
Cc: jgarzik@pobox.com, christoph@graphe.net, nirajk@calsoftinc.com,
christoph@lameter.com, Shai@Scalex86.org
Subject: Re: [patch 05/13] remove last_rx update from loopback device
Date: Tue, 15 Mar 2005 17:49:22 -0800 [thread overview]
Message-ID: <423790A2.2000906@hp.com> (raw)
In-Reply-To: <42378A8D.7090801@us.ibm.com>
Nivedita Singhvi wrote:
> Rick Jones wrote:
>
>>> These loopback driver SMP optimizations are starting to really
>>> driver me crazy.
>>
>>
>>
>> Correct or not, I suspect there are a non-trivial number of folks out
>> there who use loopback performance as an indicator of over the network
>> performance or at least of stack path length (less driver).
>
>
> I hope not the former. Given that loopback performance is
> *significantly* faster than network performance, increasing the
> performance of the loopback driver in these somewhat artificial
> ways (that differ from the real network device path) simply
> *increases* the inaccuracy of their testing and the conclusions
> they can draw from it ;).
I suspect the idea is that if loopback on Platform A is faster than loopback on
Platform B, then over the network will be faster (or at least more efficient) on
Platform A than it is on Platform B.
It is indeed fraught with numerous pitfalls - different MTU's, shorticircuting
at different places etc etc.
I do not claim to condone (even if I'm sometimes forced into that situation
myself :( ) merely to explain.
As for the 512 CPU machine mentioned in another message, at the rate cores per
die may increase over the next few years, that may not really be all that large
a box... :)
rick jones
prev parent reply other threads:[~2005-03-16 1:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 22:22 [patch 05/13] remove last_rx update from loopback device akpm
2005-03-15 22:41 ` Jeff Garzik
2005-03-15 23:08 ` Andrew Morton
2005-03-16 0:53 ` David S. Miller
2005-03-16 1:04 ` Rick Jones
2005-03-16 1:17 ` David S. Miller
2005-03-16 1:23 ` Nivedita Singhvi
2005-03-16 1:49 ` Rick Jones [this message]
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=423790A2.2000906@hp.com \
--to=rick.jones2@hp.com \
--cc=Shai@Scalex86.org \
--cc=christoph@graphe.net \
--cc=christoph@lameter.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=nirajk@calsoftinc.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).