DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Manoj Viswanath <manoj.viswanath@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Ports not detected by IGB_UIO in DPDK 1.7.1 in QEMU_KVM environment
Date: Wed, 12 Nov 2014 14:12:12 +0000	[thread overview]
Message-ID: <20141112141211.GA6688@bricha3-MOBL3> (raw)
In-Reply-To: <CAC1b25pK0CVmsAAKmMP-WnKt4sc07NOJ0yYh+o-NrkT8WcT74A@mail.gmail.com>

On Tue, Nov 11, 2014 at 07:18:32PM +0530, Manoj Viswanath wrote:
> Bruce,
> 
> Thanks for the input.
> Sure, will figure out the offending file behind this error and update this
> thread.
> 
> Meanwhile, wanted to share one more observation regarding this issue:
> The "file descriptor error" is NOT SEEN with DPDK 1.7.0 (dpdk-1.7.0.tar.gz
> <http://dpdk.org/browse/dpdk/snapshot/dpdk-1.7.0.tar.gz>) when explicitly
> binding NICs to IGB_UIO using the .py script.
> 
> The issue is only seen when using DPDK 1.7.1 ( dpdk-1.7.1.tar.gz
> <http://dpdk.org/browse/dpdk/snapshot/dpdk-1.7.1.tar.gz>). I hope the
> version i am using is the last official tag in the 1.7.x tree.
> 

Given that it's narrowed down to a change between 1.7.0 and 1.7.1 would it also
be possible for you to use git bisect to track down the commit that introduces
the error?

/Bruce

      reply	other threads:[~2014-11-12 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAC1b25pX3R2y_Cjp5UAdL6Bozrf01OkG6U6LGQvJ2aUTDXGvSA@mail.gmail.com>
2014-11-05 10:12 ` Bruce Richardson
2014-11-07 15:01   ` Manoj Viswanath
     [not found]     ` <20141107153053.GA10376@bricha3-MOBL3>
2014-11-07 17:56       ` Manoj Viswanath
2014-11-10 10:58         ` Bruce Richardson
2014-11-11 13:48           ` Manoj Viswanath
2014-11-12 14:12             ` Bruce Richardson [this message]

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=20141112141211.GA6688@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=manoj.viswanath@gmail.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).