From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] examples: fix symmetric_mp, set NIC rx_drop_en bit
Date: Thu, 4 Dec 2014 16:06:20 +0000 [thread overview]
Message-ID: <20141204160619.GA10704@bricha3-MOBL3> (raw)
In-Reply-To: <6007845.LEvoKu9qPf@xps13>
On Thu, Dec 04, 2014 at 04:36:42PM +0100, Thomas Monjalon wrote:
> 2014-12-04 14:03, Bruce Richardson:
> > On Thu, Dec 04, 2014 at 02:37:15PM +0100, Thomas Monjalon wrote:
> > > 2014-12-03 16:56, Bruce Richardson:
> > > > The symmetric_mp example app is set up to allow two processes to
> > > > share a NIC port, with each pulling packets from one queue. In order
> > > > to have the app continue working when one of the process dies, the
> > > > drop_en bit should be set in the NIC configuration. Without this bit
> > > > set, the NIC will stall once any queue fills. With the bit set, once
> > > > a queue fills, all subsequent packets for that queue are discarded
> > > > allowing other queues to continue operating as normal.
> > > >
> > > > This setting was missed when converting to use standardised defaults
> > > > in commit 81f7ecd9.
> > >
> > > I don't see rx_drop_en in commit 81f7ecd9.
> > > Why do you say it was missed?
> > >
> > This is the one app that needs the drop_en bit set, and the bit is not set in the
> > defaults. Therefore, when this app was converted to use the defaults from the
> > driver, the drop_en bit should have been explicitly set as in this patch. [The
> > fact of there being no drop_en bit in the commit is proof of its absense :-)].
>
> So you agree this bit was never been set for this app?
> Therefore I should remove the last sentence of your commit log before applying?
>
>
Oh, now I get your point. Looking at 1.7 release, yes, this bit was never set
but should really have been set. Therefore, please remove the last line as you
suggest.
/Bruce
next prev parent reply other threads:[~2014-12-04 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 16:56 Bruce Richardson
2014-12-04 13:37 ` Thomas Monjalon
2014-12-04 14:03 ` Bruce Richardson
2014-12-04 15:36 ` Thomas Monjalon
2014-12-04 16:06 ` Bruce Richardson [this message]
2014-12-05 16:21 ` 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=20141204160619.GA10704@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).