From: Song Liu <songliubraving@fb.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
"Alexei Starovoitov" <ast@kernel.org>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next] net: remove bypassed check in sch_direct_xmit()
Date: Tue, 29 May 2018 17:02:07 +0000 [thread overview]
Message-ID: <1C6C58DD-456F-4154-A9EC-EF1529DD0AF6@fb.com> (raw)
In-Reply-To: <00399207-8196-1766-330d-624f2ed35c89@cogentembedded.com>
> On May 29, 2018, at 1:58 AM, Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> wrote:
>
> Hello!
>
> On 5/29/2018 12:36 AM, Song Liu wrote:
>
>> Check sch_direct_xmit() at the end of sch_direct_xmit() will be bypassed.
>
> "Checking netif_xmit_frozen_or_stopped()", perhaps? Else it doesn't make much sense...
Thanks Sergei!
Sending v2 with fix.
Song
>
>> This is because "ret" from sch_direct_xmit() will be either NETDEV_TX_OK
>> or NETDEV_TX_BUSY, and only ret == NETDEV_TX_OK == 0 will reach the
>> condition:
>> if (ret && netif_xmit_frozen_or_stopped(txq))
>> return false;
>> This patch cleans up the code by removing the whole condition.
>> For more discussion about this, please refer to
>> https://marc.info/?t=152727195700008
>> Signed-off-by: Song Liu <songliubraving@fb.com>
>> Cc: John Fastabend <john.fastabend@gmail.com>
>> Cc: Alexei Starovoitov <ast@kernel.org>
>> Cc: David S. Miller <davem@davemloft.net>
> [...]
>
> MBR, Sergei
prev parent reply other threads:[~2018-05-29 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 21:36 [PATCH net-next] net: remove bypassed check in sch_direct_xmit() Song Liu
2018-05-29 8:58 ` Sergei Shtylyov
2018-05-29 17:02 ` Song Liu [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=1C6C58DD-456F-4154-A9EC-EF1529DD0AF6@fb.com \
--to=songliubraving@fb.com \
--cc=Kernel-team@fb.com \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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