From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH v3 3/4] net/netvsc: add documentation
Date: Wed, 18 Apr 2018 09:03:02 -0700 [thread overview]
Message-ID: <20180418090302.7ad48010@xeon-e3> (raw)
In-Reply-To: <a5bc481b-dbb6-fca2-9c3b-9dfc2bf91cd5@intel.com>
On Wed, 18 Apr 2018 14:25:22 +0100
Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> On 4/17/2018 10:53 PM, Stephen Hemminger wrote:
> > Matching documentation for new netvsc device.
> >
> > Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
> > ---
> > doc/guides/nics/index.rst | 1 +
> > doc/guides/nics/netvsc.rst | 97 ++++++++++++++++++++++++++
> > doc/guides/rel_notes/release_18_05.rst | 6 ++
> > 3 files changed, 104 insertions(+)
> > create mode 100644 doc/guides/nics/netvsc.rst
>
> Documentation added for network driver but not for bus driver, does it make
> sense to add vmbus doc too?
Not really, vmbus is only useful for one network device.
What did Dpaa2 do?
> > diff --git a/doc/guides/rel_notes/release_18_05.rst b/doc/guides/rel_notes/release_18_05.rst
> > index bc9cdda6af7a..0a7b65d49293 100644
> > --- a/doc/guides/rel_notes/release_18_05.rst
> > +++ b/doc/guides/rel_notes/release_18_05.rst
> > @@ -115,6 +115,12 @@ New Features
> >
> > Linux uevent is supported as backend of this device event notification framework.
> >
> > +* **Added experimental support for Hyper-V netvsc PMD.**
> > +
> > + The new experimntal ``netvsc`` poll mode driver provides native support for
> > + networking on Hyper-V. See the :doc:`../nics/netvsc` nic driver guide
> > + for more details on this new driver.
> > +
>
> Also there is a "Shared Library Versions" section of the release notes, the
> libraries with public API should be listed here with version information. I can
> see some bus libraries are there.
>
> If any of the libraries added has public API, should be added into that list.
The vmbus is internal.
next prev parent reply other threads:[~2018-04-18 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 21:53 [dpdk-dev] [PATCH v3 0/4] Hyper-V Netvsc PMD Stephen Hemminger
2018-04-17 21:53 ` [dpdk-dev] [PATCH v3 1/4] bus/vmbus: add hyper-v virtual bus support Stephen Hemminger
2018-04-18 13:16 ` Ferruh Yigit
2018-04-18 16:01 ` Stephen Hemminger
2018-04-17 21:53 ` [dpdk-dev] [PATCH v3 2/4] net/netvsc: add hyper-v netvsc network device Stephen Hemminger
2018-04-18 13:19 ` Ferruh Yigit
2018-04-18 16:04 ` Stephen Hemminger
2018-04-18 17:36 ` Stephen Hemminger
2018-04-17 21:53 ` [dpdk-dev] [PATCH v3 3/4] net/netvsc: add documentation Stephen Hemminger
2018-04-18 13:25 ` Ferruh Yigit
2018-04-18 16:03 ` Stephen Hemminger [this message]
2018-04-18 16:16 ` Ferruh Yigit
2018-04-19 12:37 ` Hemant Agrawal
2018-04-17 21:53 ` [dpdk-dev] [PATCH v3 4/4] bus/vmbus and net/netvsc: add meson build support Stephen Hemminger
2018-04-18 13:25 ` [dpdk-dev] [PATCH v3 0/4] Hyper-V Netvsc PMD Ferruh Yigit
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=20180418090302.7ad48010@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).