From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <marc.sune@bisdn.de>
Received: from mx.bisdn.de (mx.bisdn.de [185.27.182.31])
 by dpdk.org (Postfix) with ESMTP id 4EE2468FB
 for <dev@dpdk.org>; Sun, 19 Oct 2014 15:37:52 +0200 (CEST)
Received: from [192.168.1.43] (42.Red-79-146-253.dynamicIP.rima-tde.net
 [79.146.253.42])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx.bisdn.de (Postfix) with ESMTPSA id 8D3A0A1764
 for <dev@dpdk.org>; Sun, 19 Oct 2014 15:45:58 +0200 (CEST)
Message-ID: <5443C0B3.6060805@bisdn.de>
Date: Sun, 19 Oct 2014 15:46:27 +0200
From: Marc Sune <marc.sune@bisdn.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20131103 Icedove/17.0.10
MIME-Version: 1.0
To: dev@dpdk.org
References: <20141018225002.GA17115@mhcomputing.net>
In-Reply-To: <20141018225002.GA17115@mhcomputing.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dpdk-dev] "TX WTHRESH must be set to 0 if tx_rs_thresh is
 greater than 1"
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Oct 2014 13:37:52 -0000

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.