From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce driver name changes
Date: Fri, 22 Jul 2016 16:20:16 +0200 [thread overview]
Message-ID: <5742496.VNQb1jlzTk@xps13> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8973C9A2924@IRSMSX108.ger.corp.intel.com>
2016-07-22 14:15, De Lara Guarch, Pablo:
> From: Yigit, Ferruh
> > For physical net devices, driver name is same as folder name (mlnx5,
> > ixgbe ...)
> >
> > For virtual net devices, driver name is folder name with "eth_" prefix
> > (eth_pcap, eth_ring)
> >
> > Driver names for net devices looks consistent already, I don't know
> > about crypto devices but if crypto driver names are inconsistent what do
> > you think renaming crypto drivers only?
>
> Sure, as long as virtual Ethernet devices are consistent, I think it is ok.
> My main intention here was to have consistent (and short) driver names,
> to call rte_eal_vdev_init (or --vdev in command line).
It is important to rename every drivers with net and crypto prefixes.
The long term goal is to have a consistent command line specification
to pass parameters to any device/driver (virtual or physical).
next prev parent reply other threads:[~2016-07-22 14:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 16:56 Pablo de Lara
2016-07-11 5:08 ` Christian Ehrhardt
2016-07-22 12:37 ` De Lara Guarch, Pablo
2016-07-22 12:54 ` Adrien Mazarguil
2016-07-22 13:18 ` Ferruh Yigit
2016-07-22 14:15 ` De Lara Guarch, Pablo
2016-07-22 14:20 ` Thomas Monjalon [this message]
2016-07-22 15:13 ` Adrien Mazarguil
2016-07-27 8:30 ` Thomas Monjalon
2016-07-28 17:22 ` Maxime Coquelin
2016-07-28 17:47 ` Jerin Jacob
2016-07-28 17:54 ` Thomas Monjalon
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=5742496.VNQb1jlzTk@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=pablo.de.lara.guarch@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 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).