DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Jan Viktorin" <viktorin@rehivetech.com>
To: David Marchand <david.marchand@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Olivier Matz <olivier.matz@6wind.com>,
	Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce API changes for device objects
Date: Thu, 7 Apr 2016 19:09:50 +0200	[thread overview]
Message-ID: <20160407190950.52f58009@pcviktorin.fit.vutbr.cz> (raw)
In-Reply-To: <CALwxeUvybtxzfsMr4cQf3aNe0wZU4yuq48pPaGauQOdW_3Cz6Q@mail.gmail.com>

On Thu, 7 Apr 2016 19:00:43 +0200
David Marchand <david.marchand@6wind.com> wrote:

> On Thu, Apr 7, 2016 at 5:46 PM, Jan Viktorin <viktorin@rehivetech.com> wrote:
> > On Thu,  7 Apr 2016 17:33:17 +0200
> > David Marchand <david.marchand@6wind.com> wrote:
> >  
> >> Following discussions with Jan, here is a deprecation notice to prepare for
> >> hotplug and rte_device changes to come in 16.07.
> >>
> >> Signed-off-by: David Marchand <david.marchand@6wind.com>
> >> ---
> >>  doc/guides/rel_notes/deprecation.rst | 12 ++++++++++++
> >>  1 file changed, 12 insertions(+)
> >>
> >> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> >> index 98d5529..d749e5d 100644
> >> --- a/doc/guides/rel_notes/deprecation.rst
> >> +++ b/doc/guides/rel_notes/deprecation.rst
> >> @@ -8,6 +8,18 @@ API and ABI deprecation notices are to be posted here.
> >>  Deprecation Notices
> >>  -------------------
> >>
> >> +* The ethdev hotplug API is going to be moved to EAL with a notification
> >> +  mechanism added to crypto and ethdev libraries so that hotplug is now
> >> +  available to both of them. This API will be stripped of the device arguments
> >> +  so that it only cares about hotplugging.
> >> +
> >> +* Structures embodying pci and vdev devices are going to be reworked to
> >> +  integrate new common rte_device / rte_driver objects (see
> >> +  http://dpdk.org/ml/archives/dev/2016-January/031390.html).
> >> +  ethdev and crypto libraries will then only handle those objects so that they
> >> +  do not need to care about the kind of devices that are being used, making it
> >> +  easier to add new buses later.  
> >
> > As a result, the current rte_driver structure will be renamed to
> > rte_module and probably reworked in some way due to its semantics and
> > potential name clash with the new rte_driver struct.  
> 
> If we just introduce some macros like RTE_MODULE_INIT() /
> RTE_MODULE_EXIT(), we don't need a rte_module object at the moment ?
> 

Well, possibly, we don't need it. At least, it might be hidden and not
being a part of the API/ABI. Do you need an ack for this?

  reply	other threads:[~2016-04-07 17:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 15:33 David Marchand
2016-04-07 15:46 ` Jan Viktorin
2016-04-07 17:00   ` David Marchand
2016-04-07 17:09     ` Jan Viktorin [this message]
2016-04-07 17:24       ` David Marchand
2016-04-07 17:27 ` Jan Viktorin
2016-04-08  9:35   ` Olivier Matz
2016-04-08 15:50     ` Thomas Monjalon
2016-04-10 10:05       ` 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=20160407190950.52f58009@pcviktorin.fit.vutbr.cz \
    --to=viktorin@rehivetech.com \
    --cc=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.com \
    --cc=thomas.monjalon@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).