From: Stephen Hemminger <stephen@networkplumber.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: netvsc NAPI
Date: Wed, 22 Feb 2017 09:33:16 -0800 [thread overview]
Message-ID: <20170222093316.303203c3@xeon-e3> (raw)
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.
next reply other threads:[~2017-02-22 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 17:33 Stephen Hemminger [this message]
2017-02-23 23:24 ` netvsc NAPI David Miller
2017-02-23 23:33 ` Stephen Hemminger
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=20170222093316.303203c3@xeon-e3 \
--to=stephen@networkplumber.org \
--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).