From: Thomas Monjalon <thomas@monjalon.net>
To: Chengchang Tang <tangchengchang@huawei.com>
Cc: dev@dpdk.org, linuxarm@huawei.com, arybchenko@solarflare.com,
stephen@networkplumber.org, Ferruh Yigit <ferruh.yigit@intel.com>,
Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: add new field to rxq info struct
Date: Fri, 07 Aug 2020 23:42:17 +0200 [thread overview]
Message-ID: <2309729.UfS7YTpr3K@thomas> (raw)
In-Reply-To: <2d1a46c2-f447-d248-3432-f5f3f0a90cc4@intel.com>
07/08/2020 12:35, Ferruh Yigit:
> On 8/7/2020 11:30 AM, Chengchang Tang wrote:
> > Struct rte_eth_rxq_info will be modified to include a new field, indicating
> > the size of each buffer that could be used for HW to receive packets. Add
> > this field to rte_eth_rxq_info to expose relevant information to upper
> > layer users/application.
> >
> > For more details:
> > https://mails.dpdk.org/archives/dev/2020-July/176135.html
> >
> > Signed-off-by: Chengchang Tang <tangchengchang@huawei.com>
> > Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
> > Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> > ---
> > +* ethdev: The ``struct rte_eth_rxq_info`` struct will be modified to include
> > + a new optional field, indicating the buffer size used in receiving packets
> > + for HW. This change is planned for 20.11. For more details:
> > + https://mails.dpdk.org/archives/dev/2020-July/176135.html.
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
I think this notice is useless as the struct has __rte_cache_min_aligned.
Others have approved, so
Applied
prev parent reply other threads:[~2020-08-07 21:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 9:24 [dpdk-dev] [PATCH] doc: add new field to rxq info struct Chengchang Tang
2020-08-05 11:25 ` Andrew Rybchenko
2020-08-06 4:00 ` [dpdk-dev] [PATCH v2] " Chengchang Tang
2020-08-06 4:00 ` Chengchang Tang
2020-08-06 15:25 ` Ferruh Yigit
2020-08-07 3:51 ` Chengchang Tang
2020-08-07 7:41 ` Thomas Monjalon
2020-08-06 12:50 ` Slava Ovsiienko
2020-08-07 4:00 ` Chengchang Tang
2020-08-07 10:30 ` [dpdk-dev] [PATCH v3] " Chengchang Tang
2020-08-07 10:35 ` Ferruh Yigit
2020-08-07 21:42 ` 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=2309729.UfS7YTpr3K@thomas \
--to=thomas@monjalon.net \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=linuxarm@huawei.com \
--cc=stephen@networkplumber.org \
--cc=tangchengchang@huawei.com \
--cc=viacheslavo@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.