From: Eric Dumazet <eric.dumazet@gmail.com>
To: Vincent Ray <vray@kalrayinc.com>, linyunsheng <linyunsheng@huawei.com>
Cc: davem <davem@davemloft.net>, 方国炬 <guoju.fgj@alibaba-inc.com>,
kuba <kuba@kernel.org>, netdev <netdev@vger.kernel.org>,
"Samuel Jones" <sjones@kalrayinc.com>,
"vladimir oltean" <vladimir.oltean@nxp.com>,
"Guoju Fang" <gjfang@linux.alibaba.com>,
"Remy Gauguey" <rgauguey@kalrayinc.com>, will <will@kernel.org>,
"Eric Dumazet" <edumazet@google.com>
Subject: Re: packet stuck in qdisc : patch proposal
Date: Tue, 24 May 2022 13:17:10 -0700 [thread overview]
Message-ID: <317a3e67-0956-e9c2-0406-9349844ca612@gmail.com> (raw)
In-Reply-To: <1675198168.15239468.1653411635290.JavaMail.zimbra@kalray.eu>
On 5/24/22 10:00, Vincent Ray wrote:
> All,
>
> I confirm Eric's patch works well too, and it's better and clearer than mine.
> So I think we should go for it, and the one from Guoju in addition.
>
> @Eric : I see you are one of the networking maintainers, so I have a few questions for you :
>
> a) are you going to take care of these patches directly yourself, or is there something Guoju or I should do to promote them ?
I think this is totally fine you take ownership of the patch, please
send a formal V2.
Please double check what patchwork had to say about your V1 :
https://patchwork.kernel.org/project/netdevbpf/patch/1684598287.15044793.1653314052575.JavaMail.zimbra@kalray.eu/
And make sure to address the relevant points
The most important one is the lack of 'Signed-off-by:' tag, of course.
> b) Can we expect to see them land in the mainline soon ?
If your v2 submission is correct, it can be merged this week ;)
>
> c) Will they be backported to previous versions of the kernel ? Which ones ?
You simply can include a proper Fixes: tag, so that stable teams can
backport
the patch to all affected kernel versions.
>
> Thanks a lot, best,
Thanks a lot for working on this long standing issue.
next prev parent reply other threads:[~2022-05-24 20:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1862202329.1457162.1643113633513.JavaMail.zimbra@kalray.eu>
[not found] ` <698739062.1462023.1643115337201.JavaMail.zimbra@kalray.eu>
2022-01-28 2:36 ` packet stuck in qdisc Yunsheng Lin
2022-01-28 8:58 ` Vincent Ray
2022-01-28 9:59 ` Vincent Ray
2022-01-29 6:53 ` Yunsheng Lin
2022-01-31 18:39 ` Vincent Ray
2022-02-07 3:17 ` Yunsheng Lin
2022-03-25 6:16 ` Yunsheng Lin
2022-03-25 8:45 ` Vincent Ray
2022-04-13 13:01 ` Vincent Ray
2022-04-14 3:05 ` Guoju Fang
2022-05-23 13:54 ` packet stuck in qdisc : patch proposal Vincent Ray
2022-05-24 2:55 ` Eric Dumazet
2022-05-24 6:43 ` Yunsheng Lin
2022-05-24 8:13 ` Vincent Ray
2022-05-24 17:00 ` Vincent Ray
2022-05-24 20:17 ` Eric Dumazet [this message]
2022-05-25 9:44 ` Vincent Ray
2022-05-25 10:45 ` Yunsheng Lin
2022-05-25 12:40 ` Guoju Fang
2022-05-25 17:43 ` Vincent Ray
2022-05-25 17:48 ` Vincent Ray
2022-05-26 0:17 ` Eric Dumazet
2022-05-26 7:01 ` [PATCH v2] net: sched: add barrier to fix packet stuck problem for lockless qdisc Guoju Fang
2022-05-27 9:11 ` [PATCH v3 net] " Guoju Fang
2022-05-28 0:51 ` Yunsheng Lin
2022-05-28 10:16 ` [PATCH v4 " Guoju Fang
2022-06-01 4:00 ` patchwork-bot+netdevbpf
2022-05-30 9:36 ` packet stuck in qdisc : patch proposal Vincent Ray
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=317a3e67-0956-e9c2-0406-9349844ca612@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gjfang@linux.alibaba.com \
--cc=guoju.fgj@alibaba-inc.com \
--cc=kuba@kernel.org \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=rgauguey@kalrayinc.com \
--cc=sjones@kalrayinc.com \
--cc=vladimir.oltean@nxp.com \
--cc=vray@kalrayinc.com \
--cc=will@kernel.org \
/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).