From: Aiden Leong <aiden.leong@aibsd.com>
To: edumazet@google.com
Cc: davem@davemloft.net, eric.dumazet@gmail.com,
kernelxing@tencent.com, kuba@kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net-next 0/4] net: rps/rfs improvements
Date: Wed, 29 Mar 2023 21:17:06 +0800 [thread overview]
Message-ID: <16988771.uLZWGnKmhe@eq59> (raw)
[-- Attachment #1: Type: text/plain, Size: 2134 bytes --]
Hi Eric,
I hope my email is not too off-topic but I have some confusion on how
maintainers and should react to other people's work.
In short, you are stealing Jason's idea&&work by rewriting your implementation
which not that ethical. Since your patch is based on his work, but you only
sign-off it by your name, it's possible to raise lawsuit between Tencent and
Linux community or Google.
I'm here to provoke a conflict because we know your name in this area and I'd
to show my respect to you but I do have this kind of confusion in my mind and
wish you could explain about it.
There's another story you or Tom Herbert may be interested in: I was working
on Foo Over UDP and have implemented the missing features in the previous
company I worked for. The proposal to contribute to the upstream community was
rejected later by our boss for unhappy events very similar to this one.
Aiden Leong
> Jason Xing attempted to optimize napi_schedule_rps() by avoiding
> unneeded NET_RX_SOFTIRQ raises: [1], [2]
>
> This is quite complex to implement properly. I chose to implement
> the idea, and added a similar optimization in ____napi_schedule()
>
> Overall, in an intensive RPC workload, with 32 TX/RX queues with RFS
> I was able to observe a ~10% reduction of NET_RX_SOFTIRQ
> invocations.
>
> While this had no impact on throughput or cpu costs on this synthetic
> benchmark, we know that firing NET_RX_SOFTIRQ from softirq handler
> can force __do_softirq() to wakeup ksoftirqd when need_resched() is true.
> This can have a latency impact on stressed hosts.
>
> [1] https://lore.kernel.org/lkml/20230325152417.5403-1->
kerneljasonxing@gmail.com/
> [2] https://lore.kernel.org/netdev/20230328142112.12493-1-kerneljasonxing@gmail.com/
>
>
> Eric Dumazet (4):
> net: napi_schedule_rps() cleanup
> net: add softnet_data.in_net_rx_action
> net: optimize napi_schedule_rps()
> net: optimize ____napi_schedule() to avoid extra NET_RX_SOFTIRQ
>
> include/linux/netdevice.h | 1 +
> net/core/dev.c | 46 ++++++++++++++++++++++++++++++---------
> 2 files changed, 37 insertions(+), 10 deletions(-)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-03-29 13:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 13:17 Aiden Leong [this message]
2023-03-29 13:18 ` [PATCH net-next 0/4] net: rps/rfs improvements Aiden Leong
2023-03-29 15:33 ` Eric Dumazet
2023-03-29 16:21 ` Jason Xing
-- strict thread matches above, loose matches on Subject: below --
2023-03-28 23:50 Eric Dumazet
2023-03-29 2:40 ` Jason Xing
2023-03-30 3:04 ` Jakub Kicinski
2023-03-30 3:15 ` Eric Dumazet
2023-03-30 3:39 ` Eric Dumazet
2023-03-30 3:57 ` Jakub Kicinski
2023-03-30 12:00 ` patchwork-bot+netdevbpf
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=16988771.uLZWGnKmhe@eq59 \
--to=aiden.leong@aibsd.com \
--cc=20230328235021.1048163-1-edumazet@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).