From: Thomas Monjalon <thomas@monjalon.net>
To: "Xueming(Steven) Li" <xuemingl@nvidia.com>
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
dev@dpdk.org, Slava Ovsiienko <viacheslavo@nvidia.com>,
Ray Kinsella <mdr@ashroe.eu>, Jerin Jacob <jerinjacobk@gmail.com>,
ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH 2/2] doc: announce eth new offload flag and group field
Date: Sat, 07 Aug 2021 21:15:27 +0200 [thread overview]
Message-ID: <5155325.86dLVUaBYG@thomas> (raw)
In-Reply-To: <CALBAE1PDJ=d=ogrF8as=-Tdd75V0JhzZ4QSFALY26iOfR8OY9g@mail.gmail.com>
> > >> 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>
> > Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied, thanks.
next prev parent reply other threads:[~2021-08-07 19:15 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
2021-08-04 12:29 ` Andrew Rybchenko
2021-08-07 13:32 ` Jerin Jacob
2021-08-07 19:15 ` Thomas Monjalon [this message]
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=5155325.86dLVUaBYG@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinjacobk@gmail.com \
--cc=mdr@ashroe.eu \
--cc=viacheslavo@nvidia.com \
--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).