From: Thomas Monjalon <thomas@monjalon.net>
To: Bing Zhao <bingz@nvidia.com>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>,
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-dev] [PATCH] net/mlx5: fix loopback for DV queue
Date: Wed, 12 May 2021 17:30:41 +0200 [thread overview]
Message-ID: <3137360.tEDzu0CzRi@thomas> (raw)
In-Reply-To: <CH0PR12MB5041A879DF0FBB6CD31EFC51D0529@CH0PR12MB5041.namprd12.prod.outlook.com>
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.
How do we switch?
> > > 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:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 14:36 [dpdk-dev] [PATCH] net/mlx5: fix loopback for DV queue Bing Zhao
2021-05-12 14:48 ` Thomas Monjalon
2021-05-12 14:51 ` Bing Zhao
2021-05-12 15:30 ` Thomas Monjalon [this message]
2021-05-12 15:48 ` Slava Ovsiienko
2021-05-12 16:03 ` Thomas Monjalon
2021-05-13 11:14 ` Bing Zhao
2021-05-13 11:13 ` [dpdk-dev] [PATCH v2] " Bing Zhao
2021-05-13 12:58 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2021-05-13 12:59 ` Bing Zhao
2021-05-17 15:18 ` [dpdk-dev] [PATCH v3] " Bing Zhao
2021-05-18 8:32 ` 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=3137360.tEDzu0CzRi@thomas \
--to=thomas@monjalon.net \
--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=viacheslavo@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 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.