From: Stephen Hemminger <stephen@networkplumber.org>
To: David Miller <davem@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: netvsc NAPI
Date: Thu, 23 Feb 2017 15:33:11 -0800 [thread overview]
Message-ID: <20170223153311.7c0d99cb@xeon-e3> (raw)
In-Reply-To: <20170223.182406.911130671484909443.davem@redhat.com>
On Thu, 23 Feb 2017 18:24:06 -0500 (EST)
David Miller <davem@redhat.com> wrote:
> From: Stephen Hemminger <stephen@networkplumber.org>
> Date: Wed, 22 Feb 2017 09:33:16 -0800
>
> > NAPI for netvsc is ready but the merge coordination is a nuisance.
> >
> > Since netvsc NAPI support requires other changes that are proceeding through
> > GregKH's char-misc tree. I would like to send the two patches after current net-next
> > and char-misc-next are merged into Linus's tree.
> >
> > Need these (at a minimum) these changes
> >
> > 6e47dd3e2938 ("vmbus: expose hv_begin/end_read")
> > 5529eaf6e79a ("vmbus: remove conditional locking of vmbus_write")
> > b71e328297a3 ("vmbus: add direct isr callback mode")
> > 631e63a9f346 ("vmbus: change to per channel tasklet")
> > 37cdd991fac8 ("vmbus: put related per-cpu variable together")
> >
> > Please let me know when linux-net is up to date with these.
>
> The 'net' tree is now current with Linus's current tree, and all of
> those above commits seem to be there.
Great thanks. I will merge the NAPI and retest.
prev parent reply other threads:[~2017-02-23 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 17:33 netvsc NAPI Stephen Hemminger
2017-02-23 23:24 ` David Miller
2017-02-23 23:33 ` Stephen Hemminger [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=20170223153311.7c0d99cb@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=davem@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.