From: David Miller <davem@davemloft.net>
To: hadi@cyberus.ca
Cc: rdreier@cisco.com, xma@us.ibm.com, jgarzik@pobox.com,
netdev@vger.kernel.org, rusty@rustcorp.com.au,
shemminger@linux-foundation.org
Subject: Re: [PATCH RFC]: napi_struct V5
Date: Fri, 10 Aug 2007 14:39:14 -0700 (PDT) [thread overview]
Message-ID: <20070810.143914.18309374.davem@davemloft.net> (raw)
In-Reply-To: <1186754107.5188.32.camel@localhost>
From: jamal <hadi@cyberus.ca>
Date: Fri, 10 Aug 2007 09:55:07 -0400
> On Thu, 2007-09-08 at 09:58 -0700, Roland Dreier wrote:
>
> > Could you explain why this is unfair?
>
> The simple answer is the core attempts DRR scheduling (search for the
> paper by Varghese et al for more details)
> If you have multiple users of a resource (network interfaces in this
> case), then the quantum defines their weight. If you use more than your
> fair quota, then you are being unfair.
Actually, in the ipoib case they use less than their share :)
When they re-enable interrupts and then recheck for pending events, if
events are pending they re-disable interrupts and return immediately
instead of looping and trying to use the rest of their available
"budget" in-situ.
They do this because the time it takes to return back to the ->poll()
invoker and then call back into ->poll() the chip accumulates more
work.
If they don't do this it's really easy for them to hit cases where
they process one packet, enable interrupts, more events arrive, so
re-disable interrupts and loop, over and over again which is very
inefficient if that is in fact what happens.
To be honest, it's a workaround for the hardware design and they would
do well with even the most minimalist HW irq mitigation assist.
next prev parent reply other threads:[~2007-08-10 21:39 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
2007-08-09 16:58 ` Roland Dreier
2007-08-10 13:55 ` jamal
2007-08-10 21:39 ` David Miller [this message]
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=20070810.143914.18309374.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=jgarzik@pobox.com \
--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).