From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: fill nics features matrix for pcap
Date: Mon, 11 Apr 2016 19:07:43 +0200 [thread overview]
Message-ID: <11874060.SP5ECZ82Pk@xps13> (raw)
In-Reply-To: <20160411095232.28cf6a58@xeon-e3>
2016-04-11 09:52, Stephen Hemminger:
> I wonder if this matrix would be better if auto-generated some how.
> Either statically from source scan, or dynamically via simple app?
It would be a good exercise.
But I'm afraid the AI would be too complex to judge if the support is
enough to be valid (e.g. link speed capabilities for sub-devices,
support on architectures, content in the doc, etc).
prev parent reply other threads:[~2016-04-11 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 16:23 [dpdk-dev] [PATCH] " Ferruh Yigit
2016-04-08 16:33 ` Ferruh Yigit
2016-04-08 16:39 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2016-04-08 19:39 ` Mcnamara, John
2016-04-10 9:43 ` Thomas Monjalon
2016-04-11 16:52 ` Stephen Hemminger
2016-04-11 17:07 ` 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=11874060.SP5ECZ82Pk@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=stephen@networkplumber.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).