From: Jan Viktorin <viktorin@rehivetech.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "Viktor Puš" <pus@cesnet.cz>,
dev@dpdk.org, "Matej Vido" <matejvido@gmail.com>
Subject: Re: [dpdk-dev] Urgent - Fwd: [PATCH] doc: announce ABI change for link speed
Date: Tue, 15 Dec 2015 12:21:26 +0100 [thread overview]
Message-ID: <20151215122126.2b024806@jvn> (raw)
In-Reply-To: <D52B67DD-3646-4121-B2C2-73E5B27D898B@cesnet.cz>
Matej is aware of those changes (towards 100G) and we were discussing
this extension already. Great to see that this topic is moving on.
Jan
On Tue, 15 Dec 2015 11:56:47 +0100
Viktor Puš <pus@cesnet.cz> wrote:
> CCing to Jan in case Matej is offline today - can you ack this?
>
> Best,
> Viktor
>
> > On 15 Dec 2015, at 11:42, Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> >
> > Please, are you available to allow 100G in next DPDK release?
> > It must be accepted before releasing 2.2 (today).
> > Thanks
> >
> > 2015-12-15 08:31, Thomas Monjalon:
> >> Please ack ASAP to reach 3 acks before the release (in the coming hours).
> >> Thanks a lot
> >>
> >> -----------------------------------
> >>
> >> Objet : [PATCH] doc: announce ABI change for link speed
> >> Date : mardi 15 décembre 2015, 08:21:14
> >> De : Thomas Monjalon <thomas.monjalon@6wind.com>
> >> À : dev@dpdk.org
> >> CC : Marc Sune <marcdevel@gmail.com>, Olga Shern <olgas@mellanox.com>, Matej Vido <matejvido@gmail.com>
> >>
> >> A rework was prepared by Marc Sune:
> >> http://dpdk.org/ml/archives/dev/2015-October/026037.html
> >> The goal is to retrieve the supported link speed of a device
> >> and to allow 100G devices while having a consistent API.
> >>
> >> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> >> ---
> >> doc/guides/rel_notes/deprecation.rst | 3 +++
> >> 1 file changed, 3 insertions(+)
> >>
> >> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> >> index a4abb08..f8a41dd 100644
> >> --- a/doc/guides/rel_notes/deprecation.rst
> >> +++ b/doc/guides/rel_notes/deprecation.rst
> >> @@ -12,6 +12,9 @@ Deprecation Notices
> >> ibadcrc, ibadlen, imcasts, fdirmatch, fdirmiss,
> >> tx_pause_xon, rx_pause_xon, tx_pause_xoff, rx_pause_xoff
> >>
> >> +* The ethdev structures rte_eth_link, rte_eth_dev_info and rte_eth_conf
> >> + must be updated to support 100G link and to have a cleaner link speed API.
> >> +
> >> * ABI changes is planned for the reta field in struct rte_eth_rss_reta_entry64
> >> which handles at most 256 entries (8 bits) while newer NICs support larger
> >> tables (512 entries).
> >>
>
--
Jan Viktorin E-mail: Viktorin@RehiveTech.com
System Architect Web: www.RehiveTech.com
RehiveTech
Brno, Czech Republic
parent reply other threads:[~2015-12-15 11:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <D52B67DD-3646-4121-B2C2-73E5B27D898B@cesnet.cz>]
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=20151215122126.2b024806@jvn \
--to=viktorin@rehivetech.com \
--cc=dev@dpdk.org \
--cc=matejvido@gmail.com \
--cc=pus@cesnet.cz \
--cc=thomas.monjalon@6wind.com \
/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).