DPDK patches and discussions
 help / color / mirror / Atom feed
From: Marc Sune <marc.sune@bisdn.de>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] "TX WTHRESH must be set to 0 if tx_rs_thresh is greater than 1"
Date: Sun, 19 Oct 2014 15:46:27 +0200	[thread overview]
Message-ID: <5443C0B3.6060805@bisdn.de> (raw)
In-Reply-To: <20141018225002.GA17115@mhcomputing.net>

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-19 13:37 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 [this message]
2014-10-19 17:08   ` Matthew Hall
2014-10-20  9:36     ` Bruce Richardson
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=5443C0B3.6060805@bisdn.de \
    --to=marc.sune@bisdn.de \
    --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).