From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: NAPI and shared interrupt control
Date: Thu, 07 Dec 2006 21:56:02 +1100 [thread overview]
Message-ID: <1165488962.5027.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20061207102257.GC19479@gate.ebshome.net>
On Thu, 2006-12-07 at 02:22 -0800, Eugene Surovegin wrote:
> On Thu, Dec 07, 2006 at 02:20:10AM -0800, David Miller wrote:
> > It also just occured to me that even if you use the dummy device
> > approach, it's the dummy device's quota that will be used by the
> > generic ->poll() downcall into the driver.
>
> Yes, that's true. That's why I made this parameter
> Konfig-configurable. Yes, this is not as flexible as run-time
> configuration available for a real netdev, but better than nothing and
> nobody has complained yet :)
Can we maybe change the dummy device weight as emacs get added to a
MAL ?
Dave, the main point of my initial email was: should we provide a
routine from the net core to initialize such dummy devices properly ?
I'm a little worried that some day, the NAPI code will change and the
initialisations done by the driver will not be enough anymore...
Cheers,
Ben.
next prev parent reply other threads:[~2006-12-07 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 4:21 NAPI and shared interrupt control Benjamin Herrenschmidt
2006-12-07 4:24 ` Benjamin Herrenschmidt
2006-12-07 9:16 ` David Miller
2006-12-07 9:45 ` Eugene Surovegin
2006-12-07 9:59 ` David Miller
2006-12-07 10:15 ` Eugene Surovegin
2006-12-07 10:20 ` David Miller
2006-12-07 10:22 ` Eugene Surovegin
2006-12-07 10:56 ` Benjamin Herrenschmidt [this message]
2006-12-08 7:52 ` 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=1165488962.5027.6.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=ebs@ebshome.net \
--cc=netdev@vger.kernel.org \
/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