DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Carew, Alan" <alan.carew@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 00/10] igb_uio patches
Date: Tue, 10 Jun 2014 15:55:06 +0000	[thread overview]
Message-ID: <0E29434AEE0C3A4180987AB476A6F630593A5EC8@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20140606212644.203613327@networkplumber.org>


-----Original Message-----
From: Stephen Hemminger [mailto:stephen@networkplumber.org] 
Sent: Friday, June 06, 2014 10:27 PM
To: Carew, Alan
Cc: dev@dpkd.org
Subject: [PATCH 00/10] igb_uio patches

These apply to the current DPDK tree, and are an alternative to
the patches from Alan. It provides indication of IRQ mode via
sysfs attribute. They include cleanups and fixes to allow use
of MSI and do proper fallback for the case where MSI-X vectors
are exhausted.

Hi Stephen,

Good catches and fixes in this set, would it be possible to refactor the "enum igbuio_intr_mode" to a common header files as with http://dpdk.org/ml/archives/dev/2014-June/003127.html
With that infrastructure in place, I could resubmit my set {2,3,4} to work cleanly with yours, maintaining the same interface across user/kernel, FreeBSD and fixing Virtio also.

Regards,
Alan

       reply	other threads:[~2014-06-10 15:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140606212644.203613327@networkplumber.org>
2014-06-10 15:55 ` Carew, Alan [this message]
2014-06-10 15:59   ` Burakov, Anatoly
     [not found] ` <0E29434AEE0C3A4180987AB476A6F630593A5E2D@IRSMSX101.ger.corp.intel.com>
     [not found]   ` <20140610104035.08d3946a@nehalam.linuxnetplumber.net>
2014-06-10 19:26     ` Carew, Alan
2014-06-10 20:47       ` Stephen Hemminger
2014-06-11 10:30         ` Neil Horman
2014-06-10 20:49       ` Stephen Hemminger

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=0E29434AEE0C3A4180987AB476A6F630593A5EC8@IRSMSX101.ger.corp.intel.com \
    --to=alan.carew@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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).