From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 496D82A9 for ; Sun, 19 Oct 2014 00:42:57 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 23EB480C50B; Sat, 18 Oct 2014 15:50:02 -0700 (PDT) Date: Sat, 18 Oct 2014 15:50:02 -0700 From: Matthew Hall To: dev@dpdk.org Message-ID: <20141018225002.GA17115@mhcomputing.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Oct 2014 22:42:57 -0000 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.