From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: kys@microsoft.com, haiyangz@microsoft.com,
netdev@vger.kernel.org, sthemmin@microsoft.com
Subject: Re: [PATCH net-next 0/2] netvsc: performance regressions in net-next
Date: Wed, 22 Mar 2017 11:23:08 -0700 (PDT) [thread overview]
Message-ID: <20170322.112308.620319558265849393.davem@davemloft.net> (raw)
In-Reply-To: <20170320133152.52a7da53@xeon-e3>
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 20 Mar 2017 13:31:52 -0700
> On Mon, 20 Mar 2017 13:28:03 -0700
> Stephen Hemminger <stephen@networkplumber.org> wrote:
>
>> Fix for performance regression introduced with NAPI change;
>> and followup cleanup of vmbus core code.
>>
>> Stephen Hemminger (2):
>> netvsc: fix NAPI performance regression
>> vmbus: no longer expose iterator internals
>>
>> drivers/hv/ring_buffer.c | 51 +++++++++++++++++++++--------------------
>> drivers/net/hyperv/hyperv_net.h | 1 +
>> drivers/net/hyperv/netvsc.c | 41 +++++++++++++++------------------
>> include/linux/hyperv.h | 22 +-----------------
>> 4 files changed, 46 insertions(+), 69 deletions(-)
>>
>
> Drop this version. The code is correct the second patch causes
> clashes with some later patches. Will resend.
Oh, ok, good thing I saw this before pushing out.
Reverted.
next prev parent reply other threads:[~2017-03-22 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 20:28 [PATCH net-next 0/2] netvsc: performance regressions in net-next Stephen Hemminger
2017-03-20 20:28 ` [PATCH net-next 1/2] netvsc: fix NAPI performance regression Stephen Hemminger
2017-03-20 20:28 ` [PATCH net-next 2/2] vmbus: no longer expose iterator internals Stephen Hemminger
2017-03-20 20:31 ` [PATCH net-next 0/2] netvsc: performance regressions in net-next Stephen Hemminger
2017-03-22 18:23 ` David Miller [this message]
2017-03-22 18:22 ` 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=20170322.112308.620319558265849393.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.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).