From: John Fastabend <john.fastabend@gmail.com>
To: kongweibin <kongweibin2@huawei.com>, daniel@iogearbox.net
Cc: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, hsinweih@uci.edu,
jakub@cloudflare.com, john.fastabend@gmail.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
liuxin350@huawei.com, yanan@huawei.com, wuchangye@huawei.com,
xiesongyang@huawei.com, kongweibin2@huawei.com,
zhangmingyi5@huawei.com
Subject: RE: [bpf?] [net?] Questions about the impact of ebpf sockmap/redirection on socket performance improvement
Date: Thu, 25 May 2023 23:50:58 -0700 [thread overview]
Message-ID: <647056d28d59a_2023020887@john.notmuch> (raw)
In-Reply-To: <20230525143814.361127-1-kongweibin2@huawei.com>
kongweibin wrote:
> I'm using ebpf sockmap/redirection to bypass the TCP/IP stack to improve
> socket communication performance (throughput, latency) between different
> PODs on the same machine. As concurrent connections or payloads increase,
> there may be unconspicuous performance improvement or even performance
> degradation compared to the TCP/IP stack. I have retrieved some performance
> data, but it does not seem to involve high concurrency and high payloads,
> I would like to know if community have conducted relevant tests on these
> scenarios and have any opinions on the poor performance improvement in these
> scenarios.
Not fully following above, what is your performance test/tools and what
were the numbers?
next prev parent reply other threads:[~2023-05-26 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 14:38 [bpf?] [net?] Questions about the impact of ebpf sockmap/redirection on socket performance improvement kongweibin
2023-05-26 6:50 ` John Fastabend [this message]
2023-05-29 3:49 ` [bpf?] [net?] socket test data of ebpf sockmap/redirection and TCP/IP stack kongweibin
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=647056d28d59a_2023020887@john.notmuch \
--to=john.fastabend@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hsinweih@uci.edu \
--cc=jakub@cloudflare.com \
--cc=kongweibin2@huawei.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuxin350@huawei.com \
--cc=wuchangye@huawei.com \
--cc=xiesongyang@huawei.com \
--cc=yanan@huawei.com \
--cc=zhangmingyi5@huawei.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