From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Yong Liu <yong.liu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v4 0/7] e1000: add rx interrupt support
Date: Thu, 29 Oct 2015 19:18:32 +0100 [thread overview]
Message-ID: <1603993.a4RWodNe3S@xps13> (raw)
In-Reply-To: <1446134187-4573-1-git-send-email-yong.liu@intel.com>
2015-10-29 23:56, Yong Liu:
> This patch set will enable interrup for physical and emulated e1000 device.
> Rx queue interrupt will work with uio driver or vfio driver with msi mode.
> l3fwd-power will disable interrupt immediately when wake-up for that e1000 not
> support interrupt auto clear.
> LSC and rxq interrupt will be seperated for e1000 can only support one
> interrupt cause in the same time.
Don't you think it should be explained in a doc?
doc/guides/nics/e1000em.rst
I'm especially confused by the need of changing an example for this PMD.
Does it mean the API behaviour must be changed?
[...]
> Marvin Liu (7):
> e1000: add rx interrupt support
> e1000: separate lsc and rxq interrupt disable function
> e1000: add ethdev rxq enable and disable function
> e1000: add rxq interrupt handler
> e1000: check lsc and rxq not enable in the same time
> e1000: lsc interrupt setup function only enable itself
> l3fwd-power: disable interrupt when wake up from sleep
Announcing a support in first patch and making it work later
is a strange logic to review.
You forgot to keep the Acked-by: Cunming Liang <cunming.liang@intel.com>
Applied in this order:
e1000: restrict link interrupt setup scope
e1000: separate link and Rx interrupt disabling
e1000: support Rx interrupt setup
e1000: add Rx interrupt handler
l3fwd-power: disable Rx interrupt when waking up
Thanks
next prev parent reply other threads:[~2015-10-29 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 15:56 [PATCH v4 0/7] e1000: add rx interrupt support Yong Liu
2015-10-29 15:56 ` [PATCH v4 1/7] e1000: enable device rx queue interrupt Yong Liu
2015-10-29 15:56 ` [PATCH v4 2/7] e1000: separate lsc and rxq interrupt disable function Yong Liu
2015-10-29 15:56 ` [PATCH v4 3/7] e1000: add ethdev rxq enable and " Yong Liu
2015-10-29 15:56 ` [PATCH v4 4/7] e1000: add rxq interrupt handler Yong Liu
2015-10-29 15:56 ` [PATCH v4 5/7] e1000: check lsc and rxq not enable in the same time Yong Liu
2015-10-29 15:56 ` [PATCH v4 6/7] e1000: lsc interrupt setup function only enable itself Yong Liu
2015-10-29 15:56 ` [PATCH v4 7/7] l3fwd-power: disable interrupt when wake up from sleep Yong Liu
2015-10-29 18:18 ` Thomas Monjalon [this message]
2015-10-30 1:32 ` [PATCH v4 0/7] e1000: add rx interrupt support Liu, Yong
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=1603993.a4RWodNe3S@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=yong.liu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.