DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Liang, Ma" <liang.j.ma@intel.com>
Cc: "Rosen, Rami" <rami.rosen@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	Peter Mccarthy <peter.mccarthy@intel.com>
Subject: Re: [dpdk-dev] OPDL and 18.02 Release Notes
Date: Mon, 9 Apr 2018 15:07:21 +0100	[thread overview]
Message-ID: <ed5c2dd1-ec47-ed86-1522-ac840fccc18d@intel.com> (raw)
In-Reply-To: <20180409134312.GA23402@sivswdev01.ir.intel.com>

On 4/9/2018 2:43 PM, Liang, Ma wrote:
> On 05 Mar 17:58, Ferruh Yigit wrote:
>> On 2/9/2018 12:08 AM, Rosen, Rami wrote:
>>> Hi all,
>>> Following the recent announcement of DPDK 18.02-RC4, I went over
>>> 18.02 release notes and I have this minor query which I am not sure about:
>>> In the release notes:
>>> http://dpdk.org/doc/guides/rel_notes/release_18_02.html
>>> we have the following:
>>> ...
>>> The OPDL (Ordered Packet Distribution Library) eventdev
>>> ...
>>>
>>> While in http://dpdk.org/dev/roadmap
>>> We have:
>>> ....
>>> eventdev optimized packet distribution library (OPDL) driver
>>> ...
>>>
>>> So I am not sure about this inconsistency -should it be "optimized" or "ordered" ?
>>
>> According driver documentation (doc/guides/eventdevs/opdl.rst) it is:
>> "Ordered Packet Distribution Library", release notes seems correct.
>>
>> cc'ed maintainers.
> Hi Ferruh,
>    Team agree stay with "Ordered Packet Distribution Library" name so far. 
>    the roadmap information might need update. 

Hi Liang,

Thanks for the clarification, as long as documentation is correct nothing needs
to be done.

Thanks,
ferruh

  reply	other threads:[~2018-04-09 14:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09  0:08 Rosen, Rami
2018-03-05 17:58 ` Ferruh Yigit
2018-03-06 10:01   ` Mccarthy, Peter
2018-04-09 13:43   ` Liang, Ma
2018-04-09 14:07     ` Ferruh Yigit [this message]
2018-04-09 14:07     ` Rosen, Rami

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=ed5c2dd1-ec47-ed86-1522-ac840fccc18d@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=liang.j.ma@intel.com \
    --cc=peter.mccarthy@intel.com \
    --cc=rami.rosen@intel.com \
    --cc=thomas@monjalon.net \
    /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).