From: Jeff Garzik <jeff@garzik.org>
To: David Miller <davem@davemloft.net>, rdreier@cisco.com
Cc: hadi@cyberus.ca, xma@us.ibm.com, netdev@vger.kernel.org,
netdev-owner@vger.kernel.org, rusty@rustcorp.com.au,
shemminger@linux-foundation.org
Subject: Re: [PATCH RFC]: napi_struct V5
Date: Thu, 09 Aug 2007 01:32:24 -0400 [thread overview]
Message-ID: <46BAA6E8.4050107@garzik.org> (raw)
In-Reply-To: <20070808.212353.105403708.davem@davemloft.net>
David Miller wrote:
> From: jamal <hadi@cyberus.ca>
> Date: Wed, 08 Aug 2007 11:32:34 -0400
>
>> Think of a box where you have other network interfaces, the way you
>> are implementing currently implies you are going to be very unfair to
>> the other interfaces on the box.
>
> This was the point I was trying to make the other day.
Agreed. That's one of the big selling points of NAPI when I talk to
people -- the entire system works towards a single equilibrium, when
multiple interfaces are under load.
And conversely, without NAPI, the driver has no knowledge of conditions
outside its limited view, and resource imbalances inevitably ensue.
Particularly so for infiniband, 10gb, etc. where the natural motivation
of the driver writer appears to trend towards "performance even at the
expense of other system entities."
Jeff
next prev parent reply other threads:[~2007-08-09 5:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 6:24 [PATCH RFC]: napi_struct V5 David Miller
2007-08-06 18:00 ` Michael Chan
2007-08-06 20:50 ` David Miller
2007-08-07 12:52 ` jamal
2007-08-08 0:59 ` David Miller
2007-08-08 12:10 ` jamal
2007-08-09 4:35 ` David Miller
2007-08-07 22:37 ` Roland Dreier
2007-08-07 23:06 ` David Miller
2007-08-08 3:56 ` Roland Dreier
2007-08-08 4:08 ` David Miller
[not found] ` <OFA2F18805.38AA0BD0-ON87257331.005367FB-88257331.0027BEED@us.ibm.com>
2007-08-08 15:32 ` jamal
2007-08-09 4:23 ` David Miller
2007-08-09 5:32 ` Jeff Garzik [this message]
2007-08-09 16:58 ` Roland Dreier
2007-08-10 13:55 ` jamal
2007-08-10 21:39 ` David Miller
2007-08-13 21:47 ` Roland Dreier
2007-08-08 22:20 ` David Miller
2007-08-08 23:23 ` Shirley Ma
2007-08-09 17:49 ` Roland Dreier
2007-08-09 18:16 ` Shirley Ma
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=46BAA6E8.4050107@garzik.org \
--to=jeff@garzik.org \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=netdev-owner@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@linux-foundation.org \
--cc=xma@us.ibm.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).