DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Packet Rx issue with DPDK1.8
Date: Wed, 14 Jan 2015 17:30:15 +0100	[thread overview]
Message-ID: <2334334.VuS9a0PCxR@xps13> (raw)
In-Reply-To: <20150109092659.GA11296@bricha3-MOBL3>

2015-01-09 09:26, Bruce Richardson:
> On Fri, Jan 09, 2015 at 06:45:57AM +0000, Prashant Upadhyaya wrote:
> > Hi Bruce,
> > 
> > I tried with your suggestion.
> > 
> > When I disable the _vec function with the following config change, the
> > usecase works for me. So it points to some issue in the _vec function.
> > 
> > CONFIG_RTE_IXGBE_INC_VECTOR=y, I changed this parameter to
> > CONFIG_RTE_IXGBE_INC_VECTOR=n
> > 
> > There appears to be some gottcha in the function therefore, somebody may
> > want to run some tests again perhaps with jumbo frames enabled (and
> > sending small normal frames)
> > 
> > Regards
> > -Prashant
> 
> Yes, we'll perform additional testing and see what we can turn up.

Bruce, any news about this bug?
It seems important and could justify (with other bugs) to release a version
1.8.1.

Thanks
-- 
Thomas

  reply	other threads:[~2015-01-14 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  8:10 Prashant Upadhyaya
2015-01-08 13:47 ` Bruce Richardson
2015-01-09  6:45   ` Prashant Upadhyaya
2015-01-09  9:26     ` Bruce Richardson
2015-01-14 16:30       ` Thomas Monjalon [this message]
2015-01-14 17:01         ` Bruce Richardson
2015-01-14 18:33         ` [dpdk-dev] New to DPDK Ravi Rao
2015-01-14 19:27           ` Wiles, Keith
2015-01-14 19:54             ` Ravi Rao
     [not found]               ` <D0DC2CB2.FCE3%keith.wiles@intel.com>
2015-01-21 21:00                 ` Ravi Rao

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=2334334.VuS9a0PCxR@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.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).