DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: Jingjing Wu <jingjing.wu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] eal: add counter size for efd clean
Date: Mon, 14 Aug 2017 13:06:35 -0700	[thread overview]
Message-ID: <bb98bda0-0c93-f853-e03c-bf4238522bd7@intel.com> (raw)
In-Reply-To: <1502636600-46889-1-git-send-email-jingjing.wu@intel.com>



On 8/13/2017 8:03 AM, Jingjing Wu wrote:
> For virtual device, the rte_intr_handle struct is
> initialized by the virtual device driver, including
> the event fd assignment. If the event fd need to be
> read for clean, an argument is required for the proper
> event fd read.
>
> This patch adds efd_counter_size in rte_intr_handle
> struct to tell the rx interrupt process know the read
> size.

remove "know".

>
> Signed-off-by: Jingjing Wu <jingjing.wu@intel.com>

Besides, looks good to me.

Reviewed-by: Jianfeng Tan <jianfeng.tan@intel.com>

Thanks,
Jianfeng

> ---
>
> v2 change:
>   - fix typo and reword commit log
>
>   drivers/net/virtio/virtio_user/virtio_user_dev.c      |  2 ++
>   lib/librte_eal/linuxapp/eal/eal_interrupts.c          | 19 ++++++++++++-------
>   .../linuxapp/eal/include/exec-env/rte_interrupts.h    |  1 +
>   3 files changed, 15 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/net/virtio/virtio_user/virtio_user_dev.c b/drivers/net/virtio/virtio_user/virtio_user_dev.c
> index 7941271..906d7a2 100644
> --- a/drivers/net/virtio/virtio_user/virtio_user_dev.c
> +++ b/drivers/net/virtio/virtio_user/virtio_user_dev.c
> @@ -270,6 +270,8 @@ virtio_user_fill_intr_handle(struct virtio_user_dev *dev)
>   	eth_dev->intr_handle->nb_efd = dev->max_queue_pairs;
>   	eth_dev->intr_handle->max_intr = dev->max_queue_pairs + 1;
>   	eth_dev->intr_handle->type = RTE_INTR_HANDLE_VDEV;
> +	/* For virtio vdev, no need to read counter for clean */
> +	eth_dev->intr_handle->efd_counter_size = 0;
>   	if (dev->vhostfd >= 0)
>   		eth_dev->intr_handle->fd = dev->vhostfd;
>   
> diff --git a/lib/librte_eal/linuxapp/eal/eal_interrupts.c b/lib/librte_eal/linuxapp/eal/eal_interrupts.c
> index 3e9ac41..7de39c3 100644
> --- a/lib/librte_eal/linuxapp/eal/eal_interrupts.c
> +++ b/lib/librte_eal/linuxapp/eal/eal_interrupts.c
> @@ -914,7 +914,7 @@ static void
>   eal_intr_proc_rxtx_intr(int fd, const struct rte_intr_handle *intr_handle)
>   {
>   	union rte_intr_read_buffer buf;
> -	int bytes_read = 1;
> +	int bytes_read = 0;
>   	int nbytes;
>   
>   	switch (intr_handle->type) {
> @@ -930,11 +930,9 @@ eal_intr_proc_rxtx_intr(int fd, const struct rte_intr_handle *intr_handle)
>   		break;
>   #endif
>   	case RTE_INTR_HANDLE_VDEV:
> -		/* for vdev, fd points to:
> -		 * a. eventfd which does not need to read out;
> -		 * b. datapath fd which needs PMD to read out.
> -		 */
> -		return;
> +		bytes_read = intr_handle->efd_counter_size;
> +		/* For vdev, number of bytes to read is set by driver */
> +		break;
>   	case RTE_INTR_HANDLE_EXT:
>   		return;
>   	default:
> @@ -947,6 +945,8 @@ eal_intr_proc_rxtx_intr(int fd, const struct rte_intr_handle *intr_handle)
>   	 * read out to clear the ready-to-be-read flag
>   	 * for epoll_wait.
>   	 */
> +	if (bytes_read == 0)
> +		return;
>   	do {
>   		nbytes = read(fd, &buf, bytes_read);
>   		if (nbytes < 0) {
> @@ -1206,7 +1206,12 @@ rte_intr_efd_enable(struct rte_intr_handle *intr_handle, uint32_t nb_efd)
>   		intr_handle->nb_efd   = n;
>   		intr_handle->max_intr = NB_OTHER_INTR + n;
>   	} else if (intr_handle->type == RTE_INTR_HANDLE_VDEV) {
> -		/* do nothing, and let vdev driver to initialize this struct */
> +		/* only check, initialization would be done in vdev driver.*/
> +		if (intr_handle->efd_counter_size >
> +		    sizeof(union rte_intr_read_buffer)) {
> +			RTE_LOG(ERR, EAL, "the efd_counter_size is oversized");
> +			return -EINVAL;
> +		}
>   	} else {
>   		intr_handle->efds[0]  = intr_handle->fd;
>   		intr_handle->nb_efd   = RTE_MIN(nb_efd, 1U);
> diff --git a/lib/librte_eal/linuxapp/eal/include/exec-env/rte_interrupts.h b/lib/librte_eal/linuxapp/eal/include/exec-env/rte_interrupts.h
> index 6daffeb..fd4ea6c 100644
> --- a/lib/librte_eal/linuxapp/eal/include/exec-env/rte_interrupts.h
> +++ b/lib/librte_eal/linuxapp/eal/include/exec-env/rte_interrupts.h
> @@ -93,6 +93,7 @@ struct rte_intr_handle {
>   	enum rte_intr_handle_type type;  /**< handle type */
>   	uint32_t max_intr;             /**< max interrupt requested */
>   	uint32_t nb_efd;               /**< number of available efd(event fd) */
> +	uint8_t efd_counter_size;      /**< size of efd counter, used for vdev */
>   	int efds[RTE_MAX_RXTX_INTR_VEC_ID];  /**< intr vectors/efds mapping */
>   	struct rte_epoll_event elist[RTE_MAX_RXTX_INTR_VEC_ID];
>   				       /**< intr vector epoll event */

  reply	other threads:[~2017-08-14 20:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11  8:34 [dpdk-dev] [PATCH] " Jingjing Wu
2017-08-13 15:03 ` [dpdk-dev] [PATCH v2] " Jingjing Wu
2017-08-14 20:06   ` Tan, Jianfeng [this message]
2017-08-24  2:10   ` [dpdk-dev] [PATCH v3] " Jingjing Wu
2017-09-04  2:49     ` Tan, Jianfeng
2017-11-07  0:41       ` Thomas Monjalon
2017-10-11 13:11     ` Thomas Monjalon
2017-10-16 10:29       ` Wu, Jingjing
2017-10-16 10:45         ` Thomas Monjalon
2017-10-24 13:38           ` Wu, Jingjing
2017-10-31 13:25             ` Wu, Jingjing

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=bb98bda0-0c93-f853-e03c-bf4238522bd7@intel.com \
    --to=jianfeng.tan@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.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).