DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] "TX WTHRESH must be set to 0 if tx_rs_thresh is greater than 1"
Date: Mon, 20 Oct 2014 10:36:01 +0100
Message-ID: <20141020093601.GA13756@BRICHA3-MOBL> (raw)
In-Reply-To: <5809CF89-13EB-4698-B4B4-AFD41897DD33@mhcomputing.net>

On Sun, Oct 19, 2014 at 10:08:29AM -0700, Matthew Hall wrote:
> 1.7.1 with a few minor clang compatibility patches in the example apps

Rather than trying to tune the results yourself, maybe you could look to 
merge in the following patch set also, to offload responsibility for the 
driver settings to the driver itself.

http://thread.gmane.org/gmane.comp.networking.dpdk.devel/6189

/Bruce

> -- 
> Sent from my mobile device.
> 
> On October 19, 2014 6:46:27 AM PDT, Marc Sune <marc.sune@bisdn.de> wrote:
> >Which DPDK version are you using
> >
> >marc
> >
> >On 19/10/14 00:50, Matthew Hall wrote:
> >> Hello,
> >>
> >> I'm just trying to understand what you're supposed to do about this
> >error to
> >> get the optiomal configuration / performance. The error message and
> >comments
> >> seem like they're designed for Intel ethernet driver hackers not
> >security
> >> hackers like myself! ;-)
> >>
> >> Note: I'm trying out the Intel 82545EM in VirtualBox because the
> >virtio-net
> >> approach didn't work, for reasons I enumerated in some previous
> >mails.
> >>
> >>      /*
> >>       * If rs_bit_thresh is greater than 1, then TX WTHRESH should be
> >>       * set to 0. If WTHRESH is greater than zero, the RS bit is
> >ignored
> >>       * by the NIC and all descriptors are written back after the NIC
> >>       * accumulates WTHRESH descriptors.
> >>       */
> >>      if (tx_conf->tx_thresh.wthresh != 0 && tx_rs_thresh != 1) {
> >>          RTE_LOG(ERR, PMD, "TX WTHRESH must be set to 0 if "
> >>              "tx_rs_thresh is greater than 1. (tx_rs_thresh=%u "
> >>              "port=%d queue=%d)\n", (unsigned int)tx_rs_thresh,
> >>                  (int)dev->data->port_id, (int)queue_idx);
> >>          return -(EINVAL);
> >>      }
> >>
> >> Thanks,
> >> Matthew.
> 

  reply	other threads:[~2014-10-20  9:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-18 22:50 Matthew Hall
2014-10-19 13:46 ` Marc Sune
2014-10-19 17:08   ` Matthew Hall
2014-10-20  9:36     ` Bruce Richardson [this message]
2014-10-20 20:29       ` Matthew Hall

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=20141020093601.GA13756@BRICHA3-MOBL \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mhall@mhcomputing.net \
    /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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git