From: Yang Yingliang <yangyingliang@huawei•com>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: David Miller <davem@davemloft•net>, <netdev@vger•kernel.org>,
<willemb@google•com>
Subject: Re: [PATCH] net: less interrupt masking in NAPI
Date: Thu, 4 Dec 2014 11:09:43 +0800 [thread overview]
Message-ID: <547FD077.4060807@huawei.com> (raw)
In-Reply-To: <1417661505.22424.1.camel@edumazet-glaptop2.roam.corp.google.com>
On 2014/12/4 10:51, Eric Dumazet wrote:
> On Thu, 2014-12-04 at 10:10 +0800, Yang Yingliang wrote:
>> On 2014/12/3 19:52, Eric Dumazet wrote:
>>> On Wed, 2014-12-03 at 17:26 +0800, Yang Yingliang wrote:
>>>
>>>> Before this patch, when a large network flow arrives, some other processes
>>>> response slowly or even don't response because the cpu is dealing with softirq.
>>>>
>>>> After this patch, under pressure, much more softirq is doing in ksoftirqd. The other
>>>> processes be scheduled.
>>>>
>>>> My system has dual core.
>>>
>>> Which NIC driver are you using ?
>>>
>> The driver we developed ourself, it's not upstreamed.
>
> Is it a NAPI driver ?
Yes.
>
> Quite frankly this patch is not a stable candidate, as it was a
> performance improvement, with some regressions in a couple of drivers.
>
OK, thanks for your reply.
next prev parent reply other threads:[~2014-12-04 3:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 14:19 [PATCH] net: less interrupt masking in NAPI Eric Dumazet
2014-11-03 17:25 ` David Miller
2014-12-03 7:31 ` Yang Yingliang
2014-12-03 7:41 ` Eric Dumazet
2014-12-03 9:26 ` Yang Yingliang
2014-12-03 11:52 ` Eric Dumazet
2014-12-04 2:10 ` Yang Yingliang
2014-12-04 2:51 ` Eric Dumazet
2014-12-04 3:09 ` Yang Yingliang [this message]
2014-12-04 5:47 ` David Miller
2015-01-10 20:27 ` Oded Gabbay
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=547FD077.4060807@huawei.com \
--to=yangyingliang@huawei$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=willemb@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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