From: Thomas Monjalon <thomas@monjalon.net>
To: Satha Rao <skoteshwar@marvell.com>
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
dev@dpdk.org, Ray Kinsella <mdr@ashroe.eu>,
dpdk-dev <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@amd.com>,
Bruce Richardson <bruce.richardson@intel.com>,
konstantin.v.ananyev@yandex.ru,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [PATCH v3] doc: announce changes to rte_eth_set_queue_rate_limit API
Date: Sat, 16 Jul 2022 20:05:09 +0200 [thread overview]
Message-ID: <3621689.MHq7AAxBmi@thomas> (raw)
In-Reply-To: <CACZ4nht+QNpGEVhp6c5aFZjM4pOTsOJJrgR8k5FEGHetZ249nw@mail.gmail.com>
15/07/2022 18:29, Ajit Khaparde:
> On Fri, Jul 15, 2022 at 7:23 AM Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru> wrote:
> >
> > On 7/15/22 16:25, skoteshwar@marvell.com wrote:
> > > From: Satha Rao <skoteshwar@marvell.com>
> > >
> > > rte_eth_set_queue_rate_limit argument rate modified to uint32_t
> > > to support more than 64Gbps.
> > >
> > > Signed-off-by: Satha Rao <skoteshwar@marvell.com>
> > > Acked-by: Jerin Jacob <jerinj@marvell.com>
[...]
> > > +* ethdev: The function ``rte_eth_set_queue_rate_limit`` takes ``rate`` in Mbps.
> > > + This parameter declared as uint16_t, queue rate limited to 64Gbps. ``rate``
> > > + parameter will be modified to uint32_t in DPDK 22.11 so that it can work for
> > > + more than 64Gbps.
> >
> > Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
With a bit of English grammar rewording,
Acked-by: Thomas Monjalon <thomas@monjalon.net>
Applied, thanks.
prev parent reply other threads:[~2022-07-16 18:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 15:32 [PATCH] doc: announce changes to rte_eth_set_queue_rate_limit api skoteshwar
2022-07-07 12:52 ` Andrew Rybchenko
2022-07-07 13:38 ` [EXT] " Satha Koteswara Rao Kottidi
2022-07-12 13:10 ` Satha Koteswara Rao Kottidi
2022-07-12 14:04 ` Thomas Monjalon
2022-07-13 4:04 ` Satha Koteswara Rao Kottidi
2022-07-13 6:26 ` [PATCH v2] " skoteshwar
2022-07-13 6:46 ` Jerin Jacob
2022-07-15 13:25 ` [PATCH v3] doc: announce changes to rte_eth_set_queue_rate_limit API skoteshwar
2022-07-15 14:23 ` Andrew Rybchenko
2022-07-15 16:29 ` Ajit Khaparde
2022-07-16 18:05 ` Thomas Monjalon [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=3621689.MHq7AAxBmi@thomas \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jerinj@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=mdr@ashroe.eu \
--cc=skoteshwar@marvell.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).