From: David Miller <davem@davemloft.net>
To: xiaosuo@gmail.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] net: rps: add the shortcut for one rps_cpus
Date: Wed, 08 Sep 2010 13:11:21 -0700 (PDT) [thread overview]
Message-ID: <20100908.131121.260074669.davem@davemloft.net> (raw)
In-Reply-To: <AANLkTik8EXfzTzJGBu9pQKQUO6WQM9p1gmr64vkQjA64@mail.gmail.com>
From: Changli Gao <xiaosuo@gmail.com>
Date: Sat, 4 Sep 2010 20:18:20 +0800
> On Sat, Sep 4, 2010 at 7:01 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>> You are 'optimizing' a very unusual case and slow down 99% of normal
>> uses.
>>
>> Normal way to handle this, is to use irq affinity and deliver interrupts
>> directly to the target cpu.
>>
>>
>
> Some pseudo network devices may share the same interrupt, such as vlan
> network devices. In this case, setting the IRQ affinity can't work.
I'm fine with this patch being in net-next-2.6 for now, so I've
applied it, thanks.
prev parent reply other threads:[~2010-09-08 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 9:12 [PATCH] net: rps: add the shortcut for one rps_cpus Changli Gao
2010-09-04 11:01 ` Eric Dumazet
2010-09-04 12:18 ` Changli Gao
2010-09-08 20:11 ` David Miller [this message]
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=20100908.131121.260074669.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=xiaosuo@gmail.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).