From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Pankaj Gupta <pagupta@vmware.com>,
jbehrens@vmware.com, yongwang@vmware.com
Cc: dev@dpdk.org
Subject: Re: [PATCH 2/8] vmxnet3: implement reta query and reta update
Date: Wed, 4 May 2022 17:23:36 +0300 [thread overview]
Message-ID: <3c968a08-113b-37f2-dbc6-1d0b62e7f5b8@oktetlabs.ru> (raw)
In-Reply-To: <20220503042257.15626-3-pagupta@vmware.com>
On 5/3/22 07:22, Pankaj Gupta wrote:
> Added reta query and reta update support for VMXNET3
>
> Tested, using testpmd, for different hardware version on ESXi 7.0 Update 2.
>
> Signed-off-by: Pankaj Gupta <pagupta@vmware.com>
> ---
> drivers/net/vmxnet3/vmxnet3_ethdev.c | 67 ++++++++++++++++++++++++++++
> 1 file changed, 67 insertions(+)
>
> diff --git a/drivers/net/vmxnet3/vmxnet3_ethdev.c b/drivers/net/vmxnet3/vmxnet3_ethdev.c
> index a7e1e5fef5..eb65499cf2 100644
> --- a/drivers/net/vmxnet3/vmxnet3_ethdev.c
> +++ b/drivers/net/vmxnet3/vmxnet3_ethdev.c
> @@ -95,6 +95,14 @@ static int vmxnet3_mac_addr_set(struct rte_eth_dev *dev,
> struct rte_ether_addr *mac_addr);
> static void vmxnet3_process_events(struct rte_eth_dev *dev);
> static void vmxnet3_interrupt_handler(void *param);
> +static int
> +vmxnet3_rss_reta_update(struct rte_eth_dev *dev,
> + struct rte_eth_rss_reta_entry64 *reta_conf,
> + uint16_t reta_size);
> +static int
> +vmxnet3_rss_reta_query(struct rte_eth_dev *dev,
> + struct rte_eth_rss_reta_entry64 *reta_conf,
> + uint16_t reta_size);
> static int vmxnet3_dev_rx_queue_intr_enable(struct rte_eth_dev *dev,
> uint16_t queue_id);
> static int vmxnet3_dev_rx_queue_intr_disable(struct rte_eth_dev *dev,
> @@ -137,6 +145,8 @@ static const struct eth_dev_ops vmxnet3_eth_dev_ops = {
> .tx_queue_release = vmxnet3_dev_tx_queue_release,
> .rx_queue_intr_enable = vmxnet3_dev_rx_queue_intr_enable,
> .rx_queue_intr_disable = vmxnet3_dev_rx_queue_intr_disable,
> + .reta_update = vmxnet3_rss_reta_update,
> + .reta_query = vmxnet3_rss_reta_query,
> };
>
> struct vmxnet3_xstats_name_off {
> @@ -1696,3 +1706,60 @@ RTE_PMD_REGISTER_PCI_TABLE(net_vmxnet3, pci_id_vmxnet3_map);
> RTE_PMD_REGISTER_KMOD_DEP(net_vmxnet3, "* igb_uio | uio_pci_generic | vfio-pci");
> RTE_LOG_REGISTER_SUFFIX(vmxnet3_logtype_init, init, NOTICE);
> RTE_LOG_REGISTER_SUFFIX(vmxnet3_logtype_driver, driver, NOTICE);
> +
> +static int
> +vmxnet3_rss_reta_update(struct rte_eth_dev *dev,
> + struct rte_eth_rss_reta_entry64 *reta_conf,
> + uint16_t reta_size)
> +{
> + int i, idx, shift;
> + struct vmxnet3_hw *hw = dev->data->dev_private;
> + struct VMXNET3_RSSConf *dev_rss_conf = hw->rss_conf;
> +
> + if (reta_size != dev_rss_conf->indTableSize) {
> + PMD_DRV_LOG(ERR,
> + "The size of hash lookup table configured (%d) doesn't match "
> + "the supported number (%d)",
> + reta_size, dev_rss_conf->indTableSize);
> + return -EINVAL;
> + }
> +
> + for (i = 0; i < reta_size; i++) {
> + idx = i / RTE_ETH_RETA_GROUP_SIZE;
> + shift = i % RTE_ETH_RETA_GROUP_SIZE;
> + if (reta_conf[idx].mask & (1ULL << shift))
Please, use RTE_BIT64(shift)
> + dev_rss_conf->indTable[i] = (uint8_t)reta_conf[idx].reta[shift];
Not a problem, but as I understand explicit type cast is not required.
> + }
> +
> + VMXNET3_WRITE_BAR1_REG(hw, VMXNET3_REG_CMD,
> + VMXNET3_CMD_UPDATE_RSSIDT);
> +
> + return 0;
> +}
> +
> +static int
> +vmxnet3_rss_reta_query(struct rte_eth_dev *dev,
> + struct rte_eth_rss_reta_entry64 *reta_conf,
> + uint16_t reta_size)
> +{
> + int i, idx, shift;
> + struct vmxnet3_hw *hw = dev->data->dev_private;
> + struct VMXNET3_RSSConf *dev_rss_conf = hw->rss_conf;
> +
> + if (reta_size != dev_rss_conf->indTableSize) {
> + PMD_DRV_LOG(ERR,
> + "Size of requested hash lookup table (%d) doesn't "
> + "match the configured size (%d)",
> + reta_size, dev_rss_conf->indTableSize);
> + return -EINVAL;
> + }
> +
> + for (i = 0; i < reta_size; i++) {
> + idx = i / RTE_ETH_RETA_GROUP_SIZE;
> + shift = i % RTE_ETH_RETA_GROUP_SIZE;
> + if (reta_conf[idx].mask & (1ULL << shift))
Use RTE_BIT64(shift)
> + reta_conf[idx].reta[shift] = dev_rss_conf->indTable[i];
> + }
> +
> + return 0;
> +}
next prev parent reply other threads:[~2022-05-04 14:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 4:22 [PATCH 0/8] vmxnet3 version V5 and V6 Pankaj Gupta
2022-05-03 4:22 ` [PATCH 1/8] vmxnet3: Added V5 support Pankaj Gupta
2022-05-03 4:22 ` [PATCH 2/8] vmxnet3: implement reta query and reta update Pankaj Gupta
2022-05-04 14:23 ` Andrew Rybchenko [this message]
2022-05-03 4:22 ` [PATCH 3/8] vmxnet3: add rx queue usage count utility Pankaj Gupta
2022-05-04 14:27 ` Andrew Rybchenko
2022-05-04 14:35 ` Morten Brørup
2022-05-04 17:58 ` Pankaj Gupta
2022-05-03 4:22 ` [PATCH 4/8] vmxnet3: add get hw version api Pankaj Gupta
2022-05-04 14:35 ` Andrew Rybchenko
2022-05-03 4:22 ` [PATCH 5/8] vmxnet3, version 6 Pankaj Gupta
2022-05-04 14:46 ` Andrew Rybchenko
2022-05-03 4:22 ` [PATCH 6/8] vmxnet3: set reta size Pankaj Gupta
2022-05-04 15:05 ` Andrew Rybchenko
2022-05-03 4:22 ` [PATCH 7/8] vmxnet3: Set packet for fragmented packet Pankaj Gupta
2022-05-04 15:07 ` Andrew Rybchenko
2022-05-04 20:40 ` Pankaj Gupta
2022-05-05 8:45 ` Andrew Rybchenko
2022-05-03 4:22 ` [PATCH 8/8] vmxnet3: Fix merge error in initialization for rxDataRing feature Pankaj Gupta
2022-05-04 15:09 ` Andrew Rybchenko
2022-05-04 20:37 ` Pankaj Gupta
2022-05-05 8:37 ` Andrew Rybchenko
2022-05-03 18:50 ` [PATCH 0/8] vmxnet3 version V5 and V6 Jochen Behrens
2022-05-04 14:28 ` Andrew Rybchenko
2022-05-19 8:04 ` [PATCH v6 0/9] net/vmxnet3: support versions 5 and 6 Andrew Rybchenko
2022-05-19 8:04 ` [PATCH v6 1/9] net/vmxnet3: add version 5 support Andrew Rybchenko
2022-05-19 8:04 ` [PATCH v6 2/9] net/vmxnet3: implement RETA query and RETA update Andrew Rybchenko
2022-05-19 8:04 ` [PATCH v6 3/9] net/vmxnet3: add Rx queue usage count utility Andrew Rybchenko
2022-05-19 8:04 ` [PATCH v6 4/9] net/vmxnet3: fix ethdev callbacks init order Andrew Rybchenko
2022-05-19 8:04 ` [PATCH v6 5/9] net/vmxnet3: report HW version on FW version get Andrew Rybchenko
2022-05-19 8:04 ` [PATCH v6 6/9] net/vmxnet3: add version 6 support Andrew Rybchenko
2022-05-19 8:04 ` [PATCH v6 7/9] net/vmxnet3: advertise RETA size in device info Andrew Rybchenko
2022-05-19 8:04 ` [PATCH v6 8/9] net/vmxnet3: set packet type for fragmented packet Andrew Rybchenko
2022-05-19 8:04 ` [PATCH v6 9/9] net/vmxnet3: fix merge error in Rx data ring initialization Andrew Rybchenko
2022-05-19 8:07 ` [PATCH v6 0/9] net/vmxnet3: support versions 5 and 6 Andrew Rybchenko
2022-05-23 20:56 ` Pankaj Gupta
2022-05-24 6:46 ` Andrew Rybchenko
-- strict thread matches above, loose matches on Subject: below --
2022-05-02 19:45 [PATCH 0/8] vmxnet3: V5 and V6 Pankaj Gupta
2022-05-02 19:45 ` [PATCH 2/8] vmxnet3: implement reta query and reta update Pankaj Gupta
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=3c968a08-113b-37f2-dbc6-1d0b62e7f5b8@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=jbehrens@vmware.com \
--cc=pagupta@vmware.com \
--cc=yongwang@vmware.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).