From: Raslan Darawsheh <rasland@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"Xueming(Steven) Li" <xuemingl@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: RE: [PATCH] net/mlx5: fix shared Rx queue segment configuration match
Date: Wed, 24 Nov 2021 16:24:37 +0000 [thread overview]
Message-ID: <DM4PR12MB531263807FDFD3AD4C28ABDECF619@DM4PR12MB5312.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211124143316.30449-1-viacheslavo@nvidia.com>
Hi,
> -----Original Message-----
> From: Slava Ovsiienko <viacheslavo@nvidia.com>
> Sent: Wednesday, November 24, 2021 4:33 PM
> To: dev@dpdk.org
> Cc: ferruh.yigit@intel.com; Xueming(Steven) Li <xuemingl@nvidia.com>;
> Raslan Darawsheh <rasland@nvidia.com>; Matan Azrad
> <matan@nvidia.com>
> Subject: [PATCH] net/mlx5: fix shared Rx queue segment configuration
> match
>
> While joining the shared Rx queue to the existing queue group the queue
> configurations is checked to be the same as it was specified in the first group
> queue creation - all shared queues should be created with identical
> configurations.
>
> During the Rx queue creation the buffer split segment configuration can be
> altered - the zero segment sizes are substituted with the actual ones,
> inherited from the pools, number of segments can be extended to cover the
> maximal packet length, etc. It means the actual queue segment configuration
> can not be used directly to match the configuration provided in the queue
> setup call.
>
> To resolve an issue we should store original parameters in the shared queue
> structure and perform the check against one these stored ones.
>
> Fixes: 09c2555303be ("net/mlx5: support shared Rx queue")
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2021-11-24 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 14:33 Viacheslav Ovsiienko
2021-11-24 16:24 ` Raslan Darawsheh [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=DM4PR12MB531263807FDFD3AD4C28ABDECF619@DM4PR12MB5312.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@nvidia.com \
--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).