From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Bing Zhao <bingz@nvidia.com>
Cc: Matan Azrad <matan@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>,
Ori Kam <orika@nvidia.com>, Raslan Darawsheh <rasland@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix loopback for DV queue
Date: Wed, 12 May 2021 15:48:36 +0000 [thread overview]
Message-ID: <DM6PR12MB37535BDC2CB31053B596D235DF529@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <3137360.tEDzu0CzRi@thomas>
Hi, Thomas
> How do we switch?
Historically mlx5 created Queues and other HW objects with Verbs.
Now we are migrating ("switched") to DevX - queues are being created with DevX calls.
If there is no E-Switch - the new DevX approach is engaged,
for E-Switch configurations we still use Verbs.
With best regards,
Slava
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, May 12, 2021 18:31
> To: Bing Zhao <bingz@nvidia.com>
> Cc: Slava Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad
> <matan@nvidia.com>; dev@dpdk.org; Ori Kam <orika@nvidia.com>; Raslan
> Darawsheh <rasland@nvidia.com>; stable@dpdk.org
> Subject: Re: [PATCH] net/mlx5: fix loopback for DV queue
>
> 12/05/2021 16:51, Bing Zhao:
> > From: Thomas Monjalon <thomas@monjalon.net>
> > > 12/05/2021 16:36, Bing Zhao:
> > > > When switching to the Devx interface, the kernel driver behavior
> > > may
> > >
> > > What do you mean by "switching"?
> >
> > I mean when changing the Rxq from Verbs API to Devx API.
>
>
> > > > be different from using Verbs. The Tx loopback cannot work
> > > properly
> > > > even if the Tx and Rx queues are configured with loopback
> > > attribute.
> > > > To support self loopback for Tx, a Verbs dummy queue pair needs to
> > > be
> > > > created to trigger the kernel to enable the loopback.
> > > >
> > > > This is only required when TIR is created for Rx and loopback is
> > > > needed. Only CQ and QP are needed for this case, no WQ(RQ) needs
> > > to be
> > > > created.
>
>
next prev parent reply other threads:[~2021-05-12 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 14:36 Bing Zhao
2021-05-12 14:48 ` Thomas Monjalon
2021-05-12 14:51 ` Bing Zhao
2021-05-12 15:30 ` Thomas Monjalon
2021-05-12 15:48 ` Slava Ovsiienko [this message]
2021-05-12 16:03 ` Thomas Monjalon
2021-05-13 11:14 ` Bing Zhao
2021-05-13 11:13 ` [dpdk-stable] [PATCH v2] " Bing Zhao
2021-05-13 12:58 ` Thomas Monjalon
2021-05-13 12:59 ` Bing Zhao
2021-05-17 15:18 ` [dpdk-stable] [PATCH v3] " Bing Zhao
2021-05-18 8:32 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2021-05-18 8:33 ` Bing Zhao
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=DM6PR12MB37535BDC2CB31053B596D235DF529@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).