From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: "Xueming(Steven) Li" <xuemingl@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Xueming(Steven) Li" <xuemingl@nvidia.com>,
Ray Kinsella <mdr@ashroe.eu>
Subject: Re: [dpdk-dev] [PATCH 2/2] doc: announce eth new offload flag and group field
Date: Wed, 4 Aug 2021 08:08:17 +0000 [thread overview]
Message-ID: <DM6PR12MB3753D9CCE29C248BBBC1D663DFF19@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210802131056.2683266-2-xuemingl@nvidia.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Xueming Li
> Sent: Monday, August 2, 2021 16:11
> Cc: dev@dpdk.org; Xueming(Steven) Li <xuemingl@nvidia.com>; Ray Kinsella
> <mdr@ashroe.eu>
> Subject: [dpdk-dev] [PATCH 2/2] doc: announce eth new offload flag and
> group field
>
> To support shared Rx queue, this patch announces new offload flag
> RTE_ETH_RX_OFFLOAD_SHARED_RXQ and new shared_group field to struct
> rte_eth_rxconf in DPDK v21.11.
>
> [1] mail list discussion:
> https://mails.dpdk.org/archives/dev/2021-July/215575.html
>
> Signed-off-by: Xueming Li <xuemingl@nvidia.com>
We need this change to handle shared queues - the same queue
object can be shared by multiple ports, and releasing routine should
know exactly on which port_id/queue_id object is being released.
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
next prev parent reply other threads:[~2021-08-04 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 13:10 [dpdk-dev] [PATCH 1/2] doc: announce eth queue release callback parameter change Xueming Li
2021-08-02 13:10 ` [dpdk-dev] [PATCH 2/2] doc: announce eth new offload flag and group field Xueming Li
2021-08-04 8:08 ` Slava Ovsiienko [this message]
2021-08-04 12:29 ` Andrew Rybchenko
2021-08-07 13:32 ` Jerin Jacob
2021-08-07 19:15 ` Thomas Monjalon
2021-08-04 12:27 ` [dpdk-dev] [PATCH 1/2] doc: announce eth queue release callback parameter change Andrew Rybchenko
2021-08-04 12:31 ` Xueming(Steven) Li
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=DM6PR12MB3753D9CCE29C248BBBC1D663DFF19@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=dev@dpdk.org \
--cc=mdr@ashroe.eu \
--cc=xuemingl@nvidia.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).