netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Andrew Morton <akpm@osdl.org>,
	jgarzik@pobox.com, netdev@oss.sgi.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:23:25 -0800	[thread overview]
Message-ID: <42378A8D.7090801@us.ibm.com> (raw)
In-Reply-To: <42378617.3080600@hp.com>

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 ;).

thanks,
Nivedita

  parent reply	other threads:[~2005-03-16  1:23 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 [this message]
2005-03-16  1:49           ` Rick Jones

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=42378A8D.7090801@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=Shai@Scalex86.org \
    --cc=akpm@osdl.org \
    --cc=christoph@graphe.net \
    --cc=christoph@lameter.com \
    --cc=davem@davemloft.net \
    --cc=jgarzik@pobox.com \
    --cc=netdev@oss.sgi.com \
    --cc=nirajk@calsoftinc.com \
    --cc=rick.jones2@hp.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).