From: Thomas Monjalon <thomas@monjalon.net>
To: Shrikrishna Khare <skhare@shri-linux.eng.vmware.com>,
Shrikrishna Khare <skhare@vmware.com>
Cc: Andrew Rybchenko <arybchenko@solarflare.com>,
Rasesh Mody <rasesh.mody@cavium.com>,
Harish Patil <harish.patil@cavium.com>,
Alejandro Lucero <alejandro.lucero@netronome.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>,
John Daley <johndale@cisco.com>,
Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
Stephen Hurd <stephen.hurd@broadcom.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Ed Czeck <ed.czeck@atomicrules.com>,
John Miller <john.miller@atomicrules.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Jing Chen <jing.d.chen@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Shijith Thotton <shijith.thotton@cavium.com>,
Srisivasubramanian Srinivasan <ssrinivasan@cavium.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Olivier Matz <olivier.matz@6wind.com>,
dev@dpdk.org
Subject: Re: DPDK ethdev/mbuf features and reviews
Date: Fri, 07 Jul 2017 22:50:58 +0200 [thread overview]
Message-ID: <2350129.489avOGxEW@xps> (raw)
In-Reply-To: <alpine.DEB.2.10.1707071210090.5989@shri-linux.eng.vmware.com>
07/07/2017 21:12, Shrikrishna Khare:
> Table 1.1 from the above 17.08 doc is missing vmxnet3. The vmxnet3 driver
> is missing from 17.05 doc as well
> (http://dpdk.readthedocs.io/en/v17.05/nics/overview.html) but it is
> present in 17.02
> (http://dpdk.readthedocs.io/en/v17.02/nics/overview.html). Not sure if I
> missed something?
Depending of your browser, you may need to scroll to the right ;)
Note: you can check old versions on dpdk.org too:
http://dpdk.org/doc/guides-17.05/nics/overview.html#id1
prev parent reply other threads:[~2017-07-07 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 9:20 DPDK ethdev/mbuf features and reviews Thomas Monjalon
2017-07-07 19:12 ` Shrikrishna Khare
2017-07-07 20:50 ` Thomas Monjalon [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=2350129.489avOGxEW@xps \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=alejandro.lucero@netronome.com \
--cc=arybchenko@solarflare.com \
--cc=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.com \
--cc=ferruh.yigit@intel.com \
--cc=harish.patil@cavium.com \
--cc=jing.d.chen@intel.com \
--cc=jingjing.wu@intel.com \
--cc=john.miller@atomicrules.com \
--cc=johndale@cisco.com \
--cc=olivier.matz@6wind.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=rasesh.mody@cavium.com \
--cc=shijith.thotton@cavium.com \
--cc=skhare@shri-linux.eng.vmware.com \
--cc=skhare@vmware.com \
--cc=ssrinivasan@cavium.com \
--cc=stephen.hurd@broadcom.com \
--cc=wenzhuo.lu@intel.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 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.