From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] ethdev: add field for device data per process
Date: Mon, 15 Oct 2018 13:58:21 +0100 [thread overview]
Message-ID: <CAD+H992gx3iGjJUOYKbWyDGSzPM2yAP3AjZK-d4iLJxAvWz8wQ@mail.gmail.com> (raw)
In-Reply-To: <554e86be-9139-f580-7d79-a0114671ecfe@solarflare.com>
On Mon, Oct 15, 2018 at 1:12 PM Andrew Rybchenko <arybchenko@solarflare.com>
wrote:
> On 10/15/18 12:00 PM, Alejandro Lucero wrote:
> > Primary and secondary processes share a per-device private data. With
> > current design it is not possible to have data per-device per-process.
> > This is required for handling properly the CPP interface inside the NFP
> > PMD with multiprocess support.
> >
> > There is also at least another PMD driver, tap, with similar
> > requirements for per-process device data.
> >
> > v2:
> > - changing library version
> > - report shared library change in release notes
> >
> > v3:
> > - fix shared library version
> >
> > Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
> > ---
> > doc/guides/rel_notes/release_18_11.rst | 1 +
> > lib/librte_ethdev/Makefile | 2 +-
> > lib/librte_ethdev/meson.build | 2 +-
> > lib/librte_ethdev/rte_ethdev_core.h | 8 +++++++-
> > 4 files changed, 10 insertions(+), 3 deletions(-)
> >
> > diff --git a/doc/guides/rel_notes/release_18_11.rst
> b/doc/guides/rel_notes/release_18_11.rst
> > index c806dc6..8b2ccad 100644
> > --- a/doc/guides/rel_notes/release_18_11.rst
> > +++ b/doc/guides/rel_notes/release_18_11.rst
> > @@ -189,6 +189,7 @@ Shared Library Versions
> > librte_acl.so.2
> > + librte_cfgfile.so.2
> > librte_cmdline.so.2
> > + + librte_ethdev.so.11
> >
> > This section is a comment. Do not overwrite or remove it.
> > =========================================================
>
> It is still wrong place. There is librte_ethdev.so.10 few lines below.
> It should be updated to add + sign and change version to 11.
>
>
Apologies for my clumsiness. It seems I was modifying the example!
I'll fix this asap.
Thanks
> <...>
>
prev parent reply other threads:[~2018-10-15 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 9:00 Alejandro Lucero
2018-10-15 12:12 ` Andrew Rybchenko
2018-10-15 12:58 ` Alejandro Lucero [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=CAD+H992gx3iGjJUOYKbWyDGSzPM2yAP3AjZK-d4iLJxAvWz8wQ@mail.gmail.com \
--to=alejandro.lucero@netronome.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.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).