DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Liang, Cunming" <cunming.liang@intel.com>
To: "Liu, Yong" <yong.liu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 0/8] interrupt mode for e1000
Date: Thu, 29 Oct 2015 10:19:55 +0000	[thread overview]
Message-ID: <D0158A423229094DA7ABF71CF2FA0DA312D92D9A@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1446110325-14148-1-git-send-email-yong.liu@intel.com>

Hi,

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Yong Liu
> Sent: Thursday, October 29, 2015 5:19 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v3 0/8] interrupt mode for e1000
> 
> 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.
> 
> The patch set is developed based on one previous patch set
> "[PATCH v1 00/11] interrupt mode for i40e"
> http://www.dpdk.org/ml/archives/dev/2015-September/023903.html
> 
> v3 changes:
>     add in release note
> 
> v2 changes:
>     describe interrupt mode work with uio and vfio+msi
>     replace attribuite __unused__ with __rte_unused
> 
> Marvin Liu (8):
>   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
>   doc: release note update for e1000 intr mode
> 
>  doc/guides/rel_notes/release_2_2.rst |   1 +
>  drivers/net/e1000/em_ethdev.c        | 181
> +++++++++++++++++++++++++++++++----
>  examples/l3fwd-power/main.c          |   1 +
>  3 files changed, 164 insertions(+), 19 deletions(-)
> 
> --
> 1.9.3

Acked-by: Cunming Liang <cunming.liang@intel.com>

  parent reply	other threads:[~2015-10-29 10:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29  9:18 Yong Liu
2015-10-29  9:18 ` [dpdk-dev] [PATCH v3 1/8] e1000: add rx interrupt support Yong Liu
2015-10-29  9:18 ` [dpdk-dev] [PATCH v3 2/8] e1000: separate lsc and rxq interrupt disable function Yong Liu
2015-10-29  9:18 ` [dpdk-dev] [PATCH v3 3/8] e1000: add ethdev rxq enable and " Yong Liu
2015-10-29  9:18 ` [dpdk-dev] [PATCH v3 4/8] e1000: add rxq interrupt handler Yong Liu
2015-10-29  9:18 ` [dpdk-dev] [PATCH v3 5/8] e1000: check lsc and rxq not enable in the same time Yong Liu
2015-10-29  9:18 ` [dpdk-dev] [PATCH v3 6/8] e1000: lsc interrupt setup function only enable itself Yong Liu
2015-10-29  9:18 ` [dpdk-dev] [PATCH v3 7/8] l3fwd-power: disable interrupt when wake up from sleep Yong Liu
2015-10-29  9:18 ` [dpdk-dev] [PATCH v3 8/8] doc: release note update for e1000 intr mode Yong Liu
2015-10-29 10:19 ` Liang, Cunming [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-29  8:57 [dpdk-dev] [PATCH v3 0/8] interrupt mode for e1000 Yong Liu

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=D0158A423229094DA7ABF71CF2FA0DA312D92D9A@shsmsx102.ccr.corp.intel.com \
    --to=cunming.liang@intel.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 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).