DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
	Alejandro Lucero <alejandro.lucero@netronome.com>,
	dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4] ethdev: add field for device data per process
Date: Tue, 16 Oct 2018 09:34:14 +0100	[thread overview]
Message-ID: <9596cdfe-e34d-a0c7-ff6a-0840f6e60d08@intel.com> (raw)
In-Reply-To: <bc14e5f8-5baf-41a1-36a5-7a13b8acd631@intel.com>

On 10/16/2018 9:27 AM, Ferruh Yigit wrote:
> On 10/15/2018 3:47 PM, Andrew Rybchenko wrote:
>> On 10/15/18 5:11 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
>>>
>>> v4:
>>>   - fix release notes
>>>
>>> Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
>>
>> Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com>
> 
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2018-10-16  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 14:11 Alejandro Lucero
2018-10-15 14:47 ` Andrew Rybchenko
2018-10-16  8:27   ` Ferruh Yigit
2018-10-16  8:34     ` Ferruh Yigit [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=9596cdfe-e34d-a0c7-ff6a-0840f6e60d08@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=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).