From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla@dpdk.org Subject: [Bug 25] Ixgbe driver sets TDH register after TXDCTL.ENABLE is set Date: Sun, 01 Apr 2018 12:59:49 +0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable To: dev@dpdk.org Return-path: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://dpdk.org/tracker/show_bug.cgi?id=3D25 Bug ID: 25 Summary: Ixgbe driver sets TDH register after TXDCTL.ENABLE is set Product: DPDK Version: unspecified Hardware: All OS: All Status: CONFIRMED Severity: normal Priority: Normal Component: ethdev Assignee: dev@dpdk.org Reporter: solal.pirelli@gmail.com Target Milestone: --- The Intel 82599 data sheet (https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/82= 599-10-gbe-controller-datasheet.pdf, =C2=A78.2.3.9.8) states that "The only time that software should write to [= the TDH] register is after a reset (hardware reset or CTRL.RST) and before enabling = the transmit function (TXDCTL.ENABLE). If software were to write to this regist= er while the transmit function was enabled, the on-chip descriptor buffers mig= ht be invalidated and the hardware could become confused". The ixgbe driver's ixgbe_dev_tx_queue_start function (http://dpdk.org/browse/dpdk/tree/drivers/net/ixgbe/ixgbe_rxtx.c?h=3Dv18.02= #n5148) first enables TXDCTL.ENABLE, then performs some admirable efforts to make s= ure it is truly enabled, and then changes TDH, ensuring that hardware confusion= can happen. --=20 You are receiving this mail because: You are the assignee for the bug.=