From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Eugene Surovegin <ebs@ebshome.net>
Subject: Re: NAPI and shared interrupt control
Date: Thu, 07 Dec 2006 15:24:06 +1100 [thread overview]
Message-ID: <1165465446.5469.189.camel@localhost.localdomain> (raw)
In-Reply-To: <1165465300.5469.187.camel@localhost.localdomain>
> What Eugene does currently, which seems to me like it's actually the
> only proper solution, is to create a separate net_device structure for
> the DMA engine and thus have a single NAPI poll & weighting for all the
> EMACs sharing a given MAL (MAL is the name of that DMA engine). This
> means that Rx from any of the channels schedules the poll, and
> interrupts can be properly masked/unmasked globally based on the
> presence/absence of work on all the channels.
Actually, another solution would be to have one of the instances do the
NAPI poll for all of them instead of creating a separate net_device for
the DMA engine...
Ben.
next prev parent reply other threads:[~2006-12-07 4:24 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 [this message]
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
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=1165465446.5469.189.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;
as well as URLs for NNTP newsgroup(s).