From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wu, Yanglong" <yanglong.wu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
"Byrne, Stephen1" <stephen1.byrne@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/ixgbe: fix TDH register setting issue
Date: Tue, 20 Nov 2018 06:02:29 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E70611532E8812@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <B73B41DFFD120A45AEE57672FCA463BA05FFFB2F@shsmsx102.ccr.corp.intel.com>
> -----Original Message-----
> From: Wu, Yanglong
> Sent: Monday, November 19, 2018 6:12 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; dev@dpdk.org
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Byrne, Stephen1
> <stephen1.byrne@intel.com>
> Subject: RE: [PATCH] net/ixgbe: fix TDH register setting issue
>
> Hi, qi
> I don't understand why dose this patch not change register write order.
> THD is write before TXDCTL.ENABL.
>
> The Intel 82599 data sheet
> (https://www.intel.com/content/dam/www/public/us/en/documents/datashe
> ets/82599-10-gbe-controller-datasheet.pdf, §8.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 register while the transmit function was
> enabled, the on-chip descriptor buffers might be invalidated and the hardware
> could become confused".
OK got it, I think you can use below commit as to fix.
commit 029fd06d40fa8cff7f562dc85d7cc4609d5c91fb
Author: Ouyang Changchun <changchun.ouyang@intel.com>
Date: Wed May 28 16:06:37 2014 +0800
ixgbe: queue start and stop
This patch implements queue start and stop functionality in IXGBE PMD;
it also enable hardware loopback for VMDQ mode in IXGBE PMD.
Signed-off-by: Ouyang Changchun <changchun.ouyang@intel.com>
Tested-by: Waterman Cao <waterman.cao@intel.com>
Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
>
> Regard
> yanglong
>
> -----Original Message-----
> From: Zhang, Qi Z
> Sent: Saturday, November 17, 2018 3:52 AM
> To: Wu, Yanglong <yanglong.wu@intel.com>; dev@dpdk.org
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Byrne, Stephen1
> <stephen1.byrne@intel.com>
> Subject: RE: [PATCH] net/ixgbe: fix TDH register setting issue
>
> Hi Yanglong:
>
> > -----Original Message-----
> > From: Wu, Yanglong
> > Sent: Thursday, November 15, 2018 6:32 PM
> > To: dev@dpdk.org
> > Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Wu, Jingjing
> > <jingjing.wu@intel.com>; Byrne, Stephen1 <stephen1.byrne@intel.com>;
> > Wu, Yanglong <yanglong.wu@intel.com>
> > Subject: [PATCH] net/ixgbe: fix TDH register setting issue
> >
> > 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 register while the transmit function
> > was enabled, the on-chip descriptor buffers might be invalidated and
> > the hardware could become confused.
> >
> > Fixes: a8cdaf0964f7 ("net/ixgbe: remove redundant queue id checks")
>
> I try to understand why this patch is going to fix above commit.
> seems the commit didn't change the register write order, and even if we go
> much early I saw the TDH register is always be written after TXDCTL.ENABL.
> Did I missed something?
> btw, I'm also curious why only TDH matters but TDT does not.
>
> > Signed-off-by: Yanglong Wu <yanglong.wu@intel.com>
> > ---
> > drivers/net/ixgbe/ixgbe_rxtx.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/ixgbe/ixgbe_rxtx.c
> > b/drivers/net/ixgbe/ixgbe_rxtx.c index 2f0262ae1..ddc7efa87 100644
> > --- a/drivers/net/ixgbe/ixgbe_rxtx.c
> > +++ b/drivers/net/ixgbe/ixgbe_rxtx.c
> > @@ -5264,6 +5264,7 @@ ixgbe_dev_tx_queue_start(struct rte_eth_dev
> > *dev, uint16_t tx_queue_id)
> > hw = IXGBE_DEV_PRIVATE_TO_HW(dev->data->dev_private);
> >
> > txq = dev->data->tx_queues[tx_queue_id];
> > + IXGBE_WRITE_REG(hw, IXGBE_TDH(txq->reg_idx), 0);
> > txdctl = IXGBE_READ_REG(hw, IXGBE_TXDCTL(txq->reg_idx));
> > txdctl |= IXGBE_TXDCTL_ENABLE;
> > IXGBE_WRITE_REG(hw, IXGBE_TXDCTL(txq->reg_idx), txdctl); @@
> > -5281,7 +5282,6 @@ ixgbe_dev_tx_queue_start(struct rte_eth_dev *dev,
> > uint16_t tx_queue_id)
> > tx_queue_id);
> > }
> > rte_wmb();
> > - IXGBE_WRITE_REG(hw, IXGBE_TDH(txq->reg_idx), 0);
> > IXGBE_WRITE_REG(hw, IXGBE_TDT(txq->reg_idx), 0);
> > dev->data->tx_queue_state[tx_queue_id] =
> > RTE_ETH_QUEUE_STATE_STARTED;
> >
> > --
> > 2.11.0
next prev parent reply other threads:[~2018-11-20 6:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 2:32 Yanglong Wu
2018-11-16 19:51 ` Zhang, Qi Z
2018-11-20 2:11 ` Wu, Yanglong
2018-11-20 6:02 ` Zhang, Qi Z [this message]
2018-11-20 5:59 ` [dpdk-dev] [PATCH v2] " Yanglong Wu
2018-11-20 19:49 ` Zhang, Qi Z
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=039ED4275CED7440929022BC67E70611532E8812@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=stephen1.byrne@intel.com \
--cc=yanglong.wu@intel.com \
/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).