From: Ali Alnubani <alialnu@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
"stable@dpdk.org" <stable@dpdk.org>
Cc: "ktraynor@redhat.com" <ktraynor@redhat.com>,
Yongseok Koh <yskoh@mellanox.com>
Subject: Re: [dpdk-stable] [PATCH v2 2/3] [18.11] net/mlx5: remove device register remap
Date: Wed, 8 Jul 2020 09:27:35 +0000 [thread overview]
Message-ID: <AM0PR05MB4401C2B0F424A50CE109AFC7D7670@AM0PR05MB4401.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1594105971-14738-2-git-send-email-viacheslavo@mellanox.com>
> -----Original Message-----
> From: stable <stable-bounces@dpdk.org> On Behalf Of Viacheslav Ovsiienko
> Sent: Tuesday, July 7, 2020 10:13 AM
> To: stable@dpdk.org
> Cc: ktraynor@redhat.com; Yongseok Koh <yskoh@mellanox.com>
> Subject: [dpdk-stable] [PATCH v2 2/3] [18.11] net/mlx5: remove device
> register remap
>
> From: Yongseok Koh <yskoh@mellanox.com>
>
> UAR (User Access Region) register does not need to be remapped for
> primary process but it should be remapped only for secondary process.
> UAR register table is in the process private structure in rte_eth_devices[],
> (struct mlx5_proc_priv *)rte_eth_devices[port_id].process_private
>
> The actual UAR table follows the data structure and the table is used for both
> Tx and Rx.
>
> For Tx, BlueFlame in UAR is used to ring the doorbell.
> MLX5_TX_BFREG(txq) is defined to get a register for the txq. Processes
> access its own private data to acquire the register from the UAR table.
>
> For Rx, the doorbell in UAR is required in arming CQ event. However, it is a
> known issue that the register isn't remapped for secondary process.
>
> Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Tested-by: Ali Alnubani <alialnu@mellanox.com>
next prev parent reply other threads:[~2020-07-08 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 7:12 [dpdk-stable] [PATCH v2 1/3] [18.11] net/mlx5: fix recursive inclusion of header file Viacheslav Ovsiienko
2020-07-07 7:12 ` [dpdk-stable] [PATCH v2 2/3] [18.11] net/mlx5: remove device register remap Viacheslav Ovsiienko
2020-07-08 9:27 ` Ali Alnubani [this message]
2020-07-07 7:12 ` [dpdk-stable] [PATCH v2 3/3] [18.11] net/mlx4: " Viacheslav Ovsiienko
2020-07-08 9:28 ` Ali Alnubani
2020-07-08 9:33 ` Kevin Traynor
2020-07-08 9:26 ` [dpdk-stable] [PATCH v2 1/3] [18.11] net/mlx5: fix recursive inclusion of header file Ali Alnubani
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=AM0PR05MB4401C2B0F424A50CE109AFC7D7670@AM0PR05MB4401.eurprd05.prod.outlook.com \
--to=alialnu@mellanox.com \
--cc=ktraynor@redhat.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@mellanox.com \
--cc=yskoh@mellanox.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).