DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Wu, Jingjing" <jingjing.wu@intel.com>
Cc: dev@dpdk.org, "Tan, Jianfeng" <jianfeng.tan@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] eal: add counter size for efd clean
Date: Tue, 07 Nov 2017 01:41:09 +0100	[thread overview]
Message-ID: <2746663.Wz2itrXseX@xps> (raw)
In-Reply-To: <ED26CBA2FAD1BF48A8719AEF02201E36512AD54C@SHSMSX103.ccr.corp.intel.com>

04/09/2017 04:49, Tan, Jianfeng:
> From: Wu, Jingjing
> > 
> > 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 the read size.
> > 
> > Signed-off-by: Jingjing Wu <jingjing.wu@intel.com>
> 
> Reviewed-by: Jianfeng Tan <jianfeng.tan@intel.com>

I am not convinced at all by the whole interrupt management codebase.
But waiting longer for applying a patch will not improve the situation :)

Applied, thanks

Reworded title:
	eal/linux: add interrupt counter size for vdev

  reply	other threads:[~2017-11-07  0:41 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
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 [this message]
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=2746663.Wz2itrXseX@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jianfeng.tan@intel.com \
    --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).