From: Ben Hutchings <bhutchings@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: multiqueue interrupts...
Date: Fri, 19 Sep 2008 12:38:01 +0100 [thread overview]
Message-ID: <1221824281.3103.8.camel@achroite> (raw)
In-Reply-To: <20080918.193815.175549834.davem@davemloft.net>
On Thu, 2008-09-18 at 19:38 -0700, David Miller wrote:
[...]
> So on a multiqueue card with 2 RX queues and 2 TX queues we'd
> have names like:
>
> eth0-rx-0
> eth0-rx-1
> eth0-tx-0
> eth0-tx-1
>
> So let's make an effort to get this done right in 2.6.28 and meanwhile
> Arjan can add the irqbalanced code.
What about the case where an interrupt is shared between RX and TX
completions? Our hardware is very flexible in this regard, but based on
performance testing prior to the introduction of TX multiqueue we
currently allocate multiple interrupts for RX completions and share the
first with TX completions.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2008-09-19 11:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 2:38 multiqueue interrupts David Miller
2008-09-19 11:38 ` Ben Hutchings [this message]
2008-09-19 12:29 ` Brice Goglin
2008-09-19 20:12 ` David Miller
2008-09-19 20:12 ` David Miller
[not found] ` <41b516cb0809191050t6c9783dele8926f697854bb1@mail.gmail.com>
2008-09-19 18:18 ` Matthew Wilcox
2008-09-19 20:14 ` David Miller
2008-09-19 20:57 ` Brandeburg, Jesse
2008-09-19 21:09 ` David Miller
2008-09-19 21:15 ` Matthew Wilcox
2008-09-19 22:11 ` Arjan van de Ven
2008-09-19 22:24 ` Andy Fleming
2008-09-19 22:28 ` Arjan van de Ven
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=1221824281.3103.8.camel@achroite \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.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).