From: "Gaëtan Rivet" <gaetan.rivet@6wind.com>
To: Moti Haimovsky <motih@mellanox.com>
Cc: ferruh.yigit@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v7 1/3] net/failsafe: register as an Rx interrupt mode PMD
Date: Thu, 25 Jan 2018 12:36:11 +0100 [thread overview]
Message-ID: <20180125113611.wu6dor3xjghkhfez@bidouze.vm.6wind.com> (raw)
In-Reply-To: <1516867635-67104-2-git-send-email-motih@mellanox.com>
Hi Moti,
Thanks for splitting the patches,
A few comments.
On Thu, Jan 25, 2018 at 10:07:13AM +0200, Moti Haimovsky wrote:
> This patch adds registering the Rx queues of the failsafe PMD with EAL
> Rx interrupts subsystem.
> Each failsafe RX queue is assigned with a unique eventfd and an enable
> interrupts flag.
> The PMD creates an interrupt vector containing the above eventfds and
> Registers it with EAL. The PMD also implements the Rx interrupts enable
> and disable interface routines.
> This patch does not implement the generation of Rx interrupts, so an
> application can now wait for failsafe Rx interrupts but it will not
> receive one.
>
> Signed-off-by: Moti Haimovsky <motih@mellanox.com>
> ---
> V6:
> Fixed typo in commit subject.
>
> V5:
> Initial version of this patch in accordance to inputs from Gaetan Rivet
> in reply to
> 1516354344-13495-2-git-send-email-motih@mellanox.com
> ---
> doc/guides/nics/features/failsafe.ini | 1 +
> drivers/net/failsafe/Makefile | 1 +
> drivers/net/failsafe/failsafe.c | 4 +
> drivers/net/failsafe/failsafe_intr.c | 138 ++++++++++++++++++++++++++++++++
> drivers/net/failsafe/failsafe_ops.c | 64 +++++++++++++++
> drivers/net/failsafe/failsafe_private.h | 9 +++
> 6 files changed, 217 insertions(+)
> create mode 100644 drivers/net/failsafe/failsafe_intr.c
>
> diff --git a/doc/guides/nics/features/failsafe.ini b/doc/guides/nics/features/failsafe.ini
> index a42e344..39ee579 100644
> --- a/doc/guides/nics/features/failsafe.ini
> +++ b/doc/guides/nics/features/failsafe.ini
> @@ -6,6 +6,7 @@
> [Features]
> Link status = Y
> Link status event = Y
> +Rx interrupt = Y
It would have been more logical to update this once everything
was properly implemented, but this is inconsequential.
> MTU update = Y
> Jumbo frame = Y
> Promiscuous mode = Y
> diff --git a/drivers/net/failsafe/Makefile b/drivers/net/failsafe/Makefile
> index ea2a8fe..91a734b 100644
> --- a/drivers/net/failsafe/Makefile
> +++ b/drivers/net/failsafe/Makefile
> @@ -46,6 +46,7 @@ SRCS-$(CONFIG_RTE_LIBRTE_PMD_FAILSAFE) += failsafe_ops.c
> SRCS-$(CONFIG_RTE_LIBRTE_PMD_FAILSAFE) += failsafe_rxtx.c
> SRCS-$(CONFIG_RTE_LIBRTE_PMD_FAILSAFE) += failsafe_ether.c
> SRCS-$(CONFIG_RTE_LIBRTE_PMD_FAILSAFE) += failsafe_flow.c
> +SRCS-$(CONFIG_RTE_LIBRTE_PMD_FAILSAFE) += failsafe_intr.c
>
> # No exported include files
>
> diff --git a/drivers/net/failsafe/failsafe.c b/drivers/net/failsafe/failsafe.c
> index cb274eb..921e656 100644
> --- a/drivers/net/failsafe/failsafe.c
> +++ b/drivers/net/failsafe/failsafe.c
> @@ -244,6 +244,10 @@
Please, can you update your git (I see 1.8, debian stable uses 2.11).
The context without the function name is really hard to follow,
especially in the devops section, where the context can be very sparse.
I need each time to follow with the file opened on the side and verify
the line numbers.
> mac->addr_bytes[2], mac->addr_bytes[3],
> mac->addr_bytes[4], mac->addr_bytes[5]);
> dev->data->dev_flags |= RTE_ETH_DEV_INTR_LSC;
> + PRIV(dev)->intr_handle = (struct rte_intr_handle){
> + .fd = -1,
> + .type = RTE_INTR_HANDLE_EXT,
> + };
> return 0;
> free_args:
> failsafe_args_free(dev);
> diff --git a/drivers/net/failsafe/failsafe_intr.c b/drivers/net/failsafe/failsafe_intr.c
> new file mode 100644
> index 0000000..54ef2f4
> --- /dev/null
> +++ b/drivers/net/failsafe/failsafe_intr.c
> @@ -0,0 +1,138 @@
> +/* SPDX-License-Identifier: BSD-3-Clause
> + * Copyright 2018 Mellanox Technologies, Ltd.
> + */
> +
> +/**
> + * @file
> + * Interrupts handling for failsafe driver.
> + */
> +
> +#include <unistd.h>
> +
> +#include "failsafe_private.h"
> +
> +/**
> + * Uninstall failsafe interrupt vector.
> + *
> + * @param priv
> + * Pointer to failsafe private structure.
> + */
> +static void
> +fs_rx_intr_vec_uninstall(struct fs_priv *priv)
> +{
> + struct rte_intr_handle *intr_handle;
> +
> + intr_handle = &priv->intr_handle;
> + if (intr_handle->intr_vec != NULL) {
> + free(intr_handle->intr_vec);
> + intr_handle->intr_vec = NULL;
> + }
> + intr_handle->nb_efd = 0;
> +}
> +
> +/**
> + * Installs failsafe interrupt vector to be registered with EAL later on.
> + *
> + * @param priv
> + * Pointer to failsafe private structure.
> + *
> + * @return
> + * 0 on success, negative errno value otherwise and rte_errno is set.
> + */
> +static int
> +fs_rx_intr_vec_install(struct fs_priv *priv)
> +{
> + unsigned int i;
> + unsigned int rxqs_n;
> + unsigned int n;
> + unsigned int count;
> + struct rte_intr_handle *intr_handle;
> +
> + rxqs_n = priv->dev->data->nb_rx_queues;
> + n = RTE_MIN(rxqs_n, (uint32_t)RTE_MAX_RXTX_INTR_VEC_ID);
> + count = 0;
> + intr_handle = &priv->intr_handle;
> + /* Allocate the interrupt vector of the failsafe Rx proxy interrupts */
> + intr_handle->intr_vec = malloc(n * sizeof(intr_handle->intr_vec[0]));
> + if (intr_handle->intr_vec == NULL) {
> + fs_rx_intr_vec_uninstall(priv);
> + rte_errno = ENOMEM;
> + ERROR("Failed to allocate memory for interrupt vector,"
> + " Rx interrupts will not be supported");
> + return -rte_errno;
> + }
> + for (i = 0; i < n; i++) {
> + struct rxq *rxq = priv->dev->data->rx_queues[i];
> +
> + /* Skip queues that cannot request interrupts. */
> + if (rxq == NULL || rxq->event_fd < 0) {
> + /* Use invalid intr_vec[] index to disable entry. */
> + intr_handle->intr_vec[i] =
> + RTE_INTR_VEC_RXTX_OFFSET +
> + RTE_MAX_RXTX_INTR_VEC_ID;
> + continue;
> + }
> + if (count >= RTE_MAX_RXTX_INTR_VEC_ID) {
> + rte_errno = E2BIG;
> + ERROR("Too many Rx queues for interrupt vector size"
> + " (%d), Rx interrupts cannot be enabled",
> + RTE_MAX_RXTX_INTR_VEC_ID);
> + fs_rx_intr_vec_uninstall(priv);
> + return -rte_errno;
> + }
> + intr_handle->intr_vec[i] = RTE_INTR_VEC_RXTX_OFFSET + count;
> + intr_handle->efds[count] = rxq->event_fd;
> + count++;
> + }
> + if (count == 0) {
> + fs_rx_intr_vec_uninstall(priv);
> + } else {
> + intr_handle->nb_efd = count;
> + intr_handle->efd_counter_size = sizeof(uint64_t);
> + }
> + return 0;
> +}
> +
> +
> +/**
> + * Uninstall failsafe Rx interrupts subsystem.
> + *
> + * @param priv
> + * Pointer to private structure.
> + *
> + * @return
> + * 0 on success, negative errno value otherwise and rte_errno is set.
> + */
> +void
> +failsafe_rx_intr_uninstall(struct rte_eth_dev *dev)
> +{
> + struct fs_priv *priv;
> +
> + priv = PRIV(dev);
> + fs_rx_intr_vec_uninstall(priv);
Why not
> + fs_rx_intr_vec_uninstall(PRIV(dev));
Here?
Is it ok to call this without having enabled the interrupts before? I
see the check on intr_conf done within intr_install, but then none is
made here.
It is probably fine right now, but what will happen once someone updates
fs_rx_intr_vec_uninstall, with potentially dangerous side-effects? It
would be safer to have a symmetric code flow on both init and uninit.
> + dev->intr_handle = NULL;
> +}
> +
> +/**
> + * Install failsafe Rx interrupts subsystem.
> + *
> + * @param priv
> + * Pointer to private structure.
> + *
> + * @return
> + * 0 on success, negative errno value otherwise and rte_errno is set.
> + */
> +int
> +failsafe_rx_intr_install(struct rte_eth_dev *dev)
> +{
> + struct fs_priv *priv = PRIV(dev);
> + const struct rte_intr_conf *const intr_conf =
> + &priv->dev->data->dev_conf.intr_conf;
> +
> + if (intr_conf->rxq == 0 || priv->intr_handle.intr_vec != NULL)
Do you plan on calling this function with
priv->intr_handle.intr_vec != NULL?
Is it a condition that should ever happen?
I think if this function was called and the vectors were already
allocated, it would be a programming mistake.
Putting an RTE_ASSERT() on the condition might be better for catching
refactoring mistakes or reorders in configuration that might happen
afterward.
> + return 0;
> + if (fs_rx_intr_vec_install(priv) < 0)
> + return -rte_errno;
> + dev->intr_handle = &priv->intr_handle;
> + return 0;
> +}
> diff --git a/drivers/net/failsafe/failsafe_ops.c b/drivers/net/failsafe/failsafe_ops.c
> index 946ac98..d6a82b3 100644
> --- a/drivers/net/failsafe/failsafe_ops.c
> +++ b/drivers/net/failsafe/failsafe_ops.c
> @@ -33,6 +33,7 @@
>
> #include <stdbool.h>
> #include <stdint.h>
> +#include <unistd.h>
>
> #include <rte_debug.h>
> #include <rte_atomic.h>
> @@ -199,6 +200,10 @@
> uint8_t i;
> int ret;
>
> + ret = failsafe_rx_intr_install(dev);
> + if (ret)
> + return ret;
> +
Supperfluous line here.
> FOREACH_SUBDEV(sdev, i, dev) {
> if (sdev->state != DEV_ACTIVE)
> continue;
> @@ -228,6 +233,7 @@
> rte_eth_dev_stop(PORT_ID(sdev));
> sdev->state = DEV_STARTED - 1;
> }
> + failsafe_rx_intr_uninstall(dev);
> }
>
> static int
> @@ -317,6 +323,8 @@
> if (queue == NULL)
> return;
> rxq = queue;
> + if (rxq->event_fd > 0)
> + close(rxq->event_fd);
> dev = rxq->priv->dev;
> FOREACH_SUBDEV_STATE(sdev, i, dev, DEV_ACTIVE)
> SUBOPS(sdev, rx_queue_release)
> @@ -333,6 +341,16 @@
> const struct rte_eth_rxconf *rx_conf,
> struct rte_mempool *mb_pool)
> {
> + /*
> + * FIXME: Add a proper interface in rte_eal_interrupts for
> + * allocating eventfd as an interrupt vector.
> + * For the time being, fake as if we are using MSIX interrupts,
> + * this will cause rte_intr_efd_enable to allocate an eventfd for us.
> + */
> + struct rte_intr_handle intr_handle = {
> + .type = RTE_INTR_HANDLE_VFIO_MSIX,
> + .efds = {-1, },
Missing space:
> + .efds = { -1, },
Regards,
--
Gaëtan Rivet
6WIND
next prev parent reply other threads:[~2018-01-25 11:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 12:41 [dpdk-dev] [PATCH] net/failsafe: add Rx interrupts Moti Haimovsky
2017-12-12 1:34 ` Stephen Hemminger
2017-12-13 13:12 ` Mordechay Haimovsky
2018-01-04 15:01 ` [dpdk-dev] [PATCH v2] " Moti Haimovsky
2018-01-17 12:54 ` [dpdk-dev] [PATCH V3] " Moti Haimovsky
2018-01-19 9:32 ` [dpdk-dev] [PATCH v4] " Moti Haimovsky
2018-01-19 9:32 ` Moti Haimovsky
2018-01-19 14:11 ` Gaëtan Rivet
2018-01-23 18:43 ` [dpdk-dev] [PATCH v5 0/3] net/failsafe: add Rx interrupts support Moti Haimovsky
2018-01-23 18:43 ` [dpdk-dev] [PATCH v5 1/3] net/failsafe: regiter as an Rx interrupt mode PMD Moti Haimovsky
2018-01-23 18:43 ` [dpdk-dev] [PATCH v5 2/3] net/failsafe: slaves Rx interrupts registration Moti Haimovsky
2018-01-24 16:12 ` [dpdk-dev] [PATCH v6 0/3] net/failsafe: add Rx interrupts support Moti Haimovsky
2018-01-24 16:12 ` [dpdk-dev] [PATCH v6 1/3] net/failsafe: register as an Rx interrupt mode PMD Moti Haimovsky
2018-01-24 16:12 ` [dpdk-dev] [PATCH v6 2/3] net/failsafe: slaves Rx interrupts registration Moti Haimovsky
2018-01-25 8:07 ` [dpdk-dev] [PATCH v7 0/3] net/failsafe: add Rx interrupts support Moti Haimovsky
2018-01-25 8:07 ` [dpdk-dev] [PATCH v7 1/3] net/failsafe: register as an Rx interrupt mode PMD Moti Haimovsky
2018-01-25 11:36 ` Gaëtan Rivet [this message]
2018-01-25 8:07 ` [dpdk-dev] [PATCH v7 2/3] net/failsafe: slaves Rx interrupts registration Moti Haimovsky
2018-01-25 11:49 ` Gaëtan Rivet
2018-01-25 8:07 ` [dpdk-dev] [PATCH v7 3/3] net/failsafe: add Rx interrupts Moti Haimovsky
2018-01-25 11:58 ` Gaëtan Rivet
2018-01-25 16:19 ` [dpdk-dev] [PATCH v8 0/3] net/failsafe: add Rx interrupts support Moti Haimovsky
2018-01-25 16:19 ` [dpdk-dev] [PATCH v8 1/3] net/failsafe: register as an Rx interrupt mode PMD Moti Haimovsky
2018-01-25 16:19 ` [dpdk-dev] [PATCH v8 2/3] net/failsafe: slaves Rx interrupts registration Moti Haimovsky
2018-01-25 16:19 ` [dpdk-dev] [PATCH v8 3/3] net/failsafe: add Rx interrupts Moti Haimovsky
2018-01-25 16:53 ` [dpdk-dev] [PATCH v8 0/3] net/failsafe: add Rx interrupts support Gaëtan Rivet
2018-01-26 18:22 ` Ferruh Yigit
2018-01-24 16:12 ` [dpdk-dev] [PATCH v6 3/3] net/failsafe: add Rx interrupts Moti Haimovsky
2018-01-23 18:43 ` [dpdk-dev] [PATCH v5 " Moti Haimovsky
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=20180125113611.wu6dor3xjghkhfez@bidouze.vm.6wind.com \
--to=gaetan.rivet@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=motih@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).