DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] devargs: announce ABI change for device parameters
Date: Wed, 10 May 2017 15:04:18 +0200	[thread overview]
Message-ID: <1539960.YVRrzX6C2B@xps> (raw)
In-Reply-To: <e6d015139a17df4e063ff2a026112208354f9666.1494420483.git.gaetan.rivet@6wind.com>

10/05/2017 14:52, Gaetan Rivet:
> The PCI and virtual bus are planned to be moved to the generic
> drivers/bus directory in v17.08. For this change to be possible, the EAL
> must be made completely independent.
> 
> The rte_devargs structure currently holds device representation internal
> to those two busses. It must be made generic before this work can be
> completed.
> 
> Instead of using either a driver name for a vdev or a PCI address for a
> PCI device, a devargs structure will have to be able to describe any
> possible device on all busses, without introducing dependencies on
> any bus-specific device representation. This will break the ABI for this
> structure.
> 
> Additionally, an evolution will occur regarding the device parsing
> from the command-line. A user must be able to set which bus will handle
> which device, and this setting is integral to the definition of a
> device.

This syntax evolution is not announced below.

> The format has not yet been formally defined, but a proposition will
> follow soon for a new command line parameter format for all devices.
> 
> Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index c2f58eb..e91fc99 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -87,3 +87,7 @@ Deprecation Notices
>  
>    - ``rte_eal_pci_detach``, replaced by using the corresponding bus generic
>      method ``detach``.
> +
> +* devargs: An ABI change is planned for 17.08 for the structure ``rte_devargs``.
> +  The current version is dependent on bus-specific device identifier, which will
> +  be made generic and abstracted, in order to make the EAL bus-agnostic.
> 

  reply	other threads:[~2017-05-10 13:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 12:52 [dpdk-dev] [PATCH 1/2] pci: deprecate PCI detach Gaetan Rivet
2017-05-10 12:52 ` [dpdk-dev] [PATCH 2/2] devargs: announce ABI change for device parameters Gaetan Rivet
2017-05-10 13:04   ` Thomas Monjalon [this message]
2017-05-10 13:02 ` [dpdk-dev] [PATCH 1/2] pci: deprecate PCI detach Thomas Monjalon
2017-05-10 15:48   ` Gaëtan Rivet
2017-05-10 15:46 ` [dpdk-dev] [PATCH v2] devargs: announce ABI change for device parameters Gaetan Rivet
2017-05-10 17:28   ` Jerin Jacob
2017-05-10 17:54   ` Stephen Hemminger
2017-05-10 21:59     ` Gaëtan Rivet
2017-05-10 18:50   ` David Marchand
2017-05-10 19:54   ` Maxime Coquelin
2017-05-10 23:14   ` 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=1539960.YVRrzX6C2B@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=gaetan.rivet@6wind.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).