From: "Mccarthy, Peter" <peter.mccarthy@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Rosen, Rami" <rami.rosen@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Ma, Liang J" <liang.j.ma@intel.com>
Subject: Re: [dpdk-dev] OPDL and 18.02 Release Notes
Date: Tue, 6 Mar 2018 10:01:07 +0000 [thread overview]
Message-ID: <B1223E5663DEAA4CB38C60CC0654E5F829E99E87@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <685f7b21-c36c-9896-36c7-c781e2390fb7@intel.com>
The O stands for "Optimized", we will make the necessary changes to remove inconsistencies.
Regards
Peter
-----Original Message-----
From: Yigit, Ferruh
Sent: Monday, March 5, 2018 5:58 PM
To: Rosen, Rami <rami.rosen@intel.com>; dev@dpdk.org
Cc: thomas@monjalon.net; Ma, Liang J <liang.j.ma@intel.com>; Mccarthy, Peter <peter.mccarthy@intel.com>
Subject: Re: [dpdk-dev] OPDL and 18.02 Release Notes
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.
>
> Regards,
> Rami Rosen
>
>
--------------------------------------------------------------
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
next prev parent reply other threads:[~2018-03-06 10:01 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 [this message]
2018-04-09 13:43 ` Liang, Ma
2018-04-09 14:07 ` Ferruh Yigit
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=B1223E5663DEAA4CB38C60CC0654E5F829E99E87@IRSMSX106.ger.corp.intel.com \
--to=peter.mccarthy@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=liang.j.ma@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).