From: Thomas Monjalon <thomas@monjalon.net>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Matan Azrad <matan@mellanox.com>
Cc: dev@dpdk.org, Ophir Munk <ophirmu@mellanox.com>,
Moti Haimovsky <motih@mellanox.com>,
Olga Shern <olgas@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx4: fix last Tx wqe stamping lack
Date: Sat, 11 Nov 2017 15:53:07 +0100 [thread overview]
Message-ID: <11709391.GH4dFWTqEr@xps> (raw)
In-Reply-To: <20171110150241.GI24849@6wind.com>
10/11/2017 16:02, Adrien Mazarguil:
> On Fri, Nov 10, 2017 at 08:27:18AM +0000, Matan Azrad wrote:
> > When Tx pakcet HW processing is done, SW should stamp all the completion
> > burst WQEs.
> >
> > Stamp missed last completion burst WQE.
> >
> > Fixes: c3c977bbecbd ("net/mlx4: add Tx bypassing Verbs")
> >
> > Signed-off-by: Matan Azrad <matan@mellanox.com>
>
> This reads like you were in a hurry :)
>
> Took me a while to understand the problem and how you addressed it. So in
> short, wqe_index is consumed but its TXBBs aren't stamped because the loop
> stops at its index without processing it.
>
> Patch looks good but could have been simpler by directly initializing
> nr_txbbs to sq->tail, not use sq->tail as an offset afterward and get rid of
> sq_tail. It's OK as this wouldn't have resulted in a smaller patch anyway.
>
> Commit log rewording suggestion:
>
> net/mlx4: fix missing stamp during Tx completion
>
> After processing completed packets, the owner bit of each TXBB comprised
> in its WQEs must be invalidated. The loop stops short of processing the
> last WQE.
>
> Other than that,
>
> Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Applied with suggested commit log, thanks
prev parent reply other threads:[~2017-11-11 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 8:27 Matan Azrad
2017-11-10 15:02 ` Adrien Mazarguil
2017-11-11 14:53 ` Thomas Monjalon [this message]
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=11709391.GH4dFWTqEr@xps \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=motih@mellanox.com \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.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).