From: "Yang, Zhiyong" <zhiyong.yang@intel.com>
To: "Horton, Remy" <remy.horton@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Tan, Jianfeng" <jianfeng.tan@intel.com>,
"yliu@fridaylinux.org" <yliu@fridaylinux.org>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2] doc: announce API and ABI change for ethdev
Date: Sat, 5 Aug 2017 10:34:40 +0000 [thread overview]
Message-ID: <E182254E98A5DA4EB1E657AC7CB9BD2A8AEE3C82@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <61ed8dc6-99f1-cfb5-a560-ac4d2f0a6657@intel.com>
Hi, Remy:
> -----Original Message-----
> From: Horton, Remy
> Sent: Friday, August 4, 2017 2:56 PM
> To: Yang, Zhiyong <zhiyong.yang@intel.com>; dev@dpdk.org
> Cc: Tan, Jianfeng <jianfeng.tan@intel.com>; yliu@fridaylinux.org;
> jerin.jacob@caviumnetworks.com; thomas@monjalon.net
> Subject: Re: [dpdk-dev] [PATCH v2] doc: announce API and ABI change for
> ethdev
>
>
> On 04/08/2017 06:27, Zhiyong Yang wrote:
> > This is an API/ABI change notice for DPDK 17.11 on redefinition of
> > port_id. port_id is defined as uint8_t by now, which is just ranged
> > from 0 to 255. For more and more scenerioes, more than 256 ports are
> > needed to support for vdev scalability.
> >
> > It is necessary for redefinition of port_id to extend from 1 bytes to
> > 2 bytes. All ethdev APIs and use cases related to port_id will be
> > changed at the same time.
>
> I think this reads a little better:
>
> This is an API/ABI change notice for DPDK 17.11 announcing the redefinition of
> port_id. port_id is currently defined as uint8_t, which is limited to the range 0 to
> 255. A larger range is required for vdev scalability.
>
> It is necessary for a redefinition of port_id to extend it from 1 bytes to 2 bytes.
> All ethdev APIs and usages related to port_id will be changed at the same time.
Thanks Remy, of course. Your statement is better. I have a lot of things to learn
when speaking in English. I hope I can describe things like you, a native speaker. :)
Thanks again for your ack.
Zhiyong
>
> > doc/guides/rel_notes/deprecation.rst | 6 ++++++
> > 1 file changed, 6 insertions(+)
>
> Acked-by: Remy Horton <remy.horton@intel.com>
next prev parent reply other threads:[~2017-08-05 10:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 7:58 [dpdk-dev] [PATCH] " Zhiyong Yang
2017-08-04 1:12 ` Tan, Jianfeng
2017-08-04 4:07 ` Yuanhan Liu
2017-08-04 4:13 ` Jerin Jacob
2017-08-04 5:36 ` Yang, Zhiyong
2017-08-04 5:27 ` [dpdk-dev] [PATCH v2] " Zhiyong Yang
2017-08-04 6:56 ` Remy Horton
2017-08-05 10:34 ` Yang, Zhiyong [this message]
2017-08-07 3:07 ` Yang, Zhiyong
2017-08-07 11:04 ` Thomas Monjalon
2017-08-07 15:20 ` Shahaf Shuler
2017-08-07 12:42 ` [dpdk-dev] [PATCH v3] " Zhiyong Yang
2017-08-08 4:02 ` Yang, Zhiyong
2017-08-08 9:35 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2017-01-05 10:44 [dpdk-dev] [PATCH v1] " Bernard Iremonger
2017-01-05 15:25 ` [dpdk-dev] [PATCH v2] " Bernard Iremonger
2017-02-13 17:57 ` Thomas Monjalon
2017-02-14 3:17 ` Jerin Jacob
2017-02-14 10:33 ` Iremonger, Bernard
2017-02-14 19:37 ` 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=E182254E98A5DA4EB1E657AC7CB9BD2A8AEE3C82@BGSMSX101.gar.corp.intel.com \
--to=zhiyong.yang@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianfeng.tan@intel.com \
--cc=remy.horton@intel.com \
--cc=thomas@monjalon.net \
--cc=yliu@fridaylinux.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).