From: "Liang, Cunming" <cunming.liang@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Nemeth, Balazs" <balazs.nemeth@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] ixgbe vector mode not working.
Date: Sat, 28 Feb 2015 03:33:52 +0000 [thread overview]
Message-ID: <D0158A423229094DA7ABF71CF2FA0DA3118E0239@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20150225170718.371163a1@urahara>
Hi Stephen,
The root cause is about the rx descriptor number.
As we use below code to quick process the rx_tail wrap, it require rxd value is a 2^n.
"rxq->rx_tail = (uint16_t)(rxq->rx_tail & (rxq->nb_rx_desc - 1));"
We should add more checking on the input rxd, if checking fail, then tend to use scalar pmd.
Thanks for the report, I'll send fix patch soon.
-Cunming
> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Thursday, February 26, 2015 9:07 AM
> To: Liang, Cunming
> Cc: Nemeth, Balazs; Richardson, Bruce; Neil Horman; dev@dpdk.org
> Subject: Re: ixgbe vector mode not working.
>
> On Wed, 25 Feb 2015 08:49:48 +0000
> "Liang, Cunming" <cunming.liang@intel.com> wrote:
>
> > Hi Stephen,
> >
> > Thanks for the info, with rxd=4000, I can reproduce it.
> > On that time, it runs out of mbuf.
> > I'll follow up this issue.
>
> The first time I ran it, the code was configure rx/tx conf
> which was leftover from older versions.
>
> Second time I ran it and the same hang happened.
> Looking at mbuf pool statistics I see that it gets exhausted,
> even when extra mbuf's are added to the pool.
>
> Looks like a memory leak.
next prev parent reply other threads:[~2015-02-28 3:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 0:16 Stephen Hemminger
2015-02-25 4:55 ` Liang, Cunming
2015-02-25 7:36 ` Stephen Hemminger
2015-02-25 8:49 ` Liang, Cunming
2015-02-26 1:07 ` Stephen Hemminger
2015-02-28 3:33 ` Liang, Cunming [this message]
2015-03-05 19:09 ` Thomas Monjalon
2015-02-25 9:18 ` Thomas Monjalon
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=D0158A423229094DA7ABF71CF2FA0DA3118E0239@shsmsx102.ccr.corp.intel.com \
--to=cunming.liang@intel.com \
--cc=balazs.nemeth@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).