From: Philo Lu <lulie@linux.alibaba.com>
To: Paolo Abeni <pabeni@redhat.com>, netdev@vger.kernel.org
Cc: willemdebruijn.kernel@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, dsahern@kernel.org,
antony.antony@secunet.com, steffen.klassert@secunet.com,
linux-kernel@vger.kernel.org, dust.li@linux.alibaba.com,
jakub@cloudflare.com, fred.cc@alibaba-inc.com,
yubing.qiuyubing@alibaba-inc.com
Subject: Re: [PATCH v4 net-next 2/3] net/udp: Add 4-tuple hash list basis
Date: Wed, 16 Oct 2024 14:30:57 +0800 [thread overview]
Message-ID: <2888bb8f-1ee4-4342-968f-82573d583709@linux.alibaba.com> (raw)
In-Reply-To: <9d611cbc-3728-463d-ba8a-5732e28b8cf4@redhat.com>
On 2024/10/14 18:07, Paolo Abeni wrote:
> Hi,
>
> On 10/12/24 03:29, Philo Lu wrote:
>> @@ -3480,13 +3486,14 @@ static struct udp_table __net_init
>> *udp_pernet_table_alloc(unsigned int hash_ent
>> if (!udptable)
>> goto out;
>> - slot_size = sizeof(struct udp_hslot) + sizeof(struct
>> udp_hslot_main);
>> + slot_size = 2 * sizeof(struct udp_hslot) + sizeof(struct
>> udp_hslot_main);
>> udptable->hash = vmalloc_huge(hash_entries * slot_size,
>> GFP_KERNEL_ACCOUNT);
>
> I'm sorry for the late feedback.
>
> I think it would be better to make the hash4 infra a no op (no lookup,
> no additional memory used) for CONFIG_BASE_SMALL=y builds.
>
Got it. There are 2 affected structs, udp_hslot and udp_sock. They (as
well as related helpers like udp4_hash4) can be wrapped with
CONFIG_BASE_SMALL, and then we can enable BASE_SMALL to eliminate
additional overhead of hash4.
```
+struct udp_hslot_main {
+ struct udp_hslot hslot; /* must be the first member */
+#if !IS_ENABLED(CONFIG_BASE_SMALL)
+ u32 hash4_cnt;
+#endif
+} __aligned(2 * sizeof(long));
@@ -56,6 +56,12 @@ struct udp_sock {
int pending; /* Any pending frames ? */
__u8 encap_type; /* Is this an Encapsulation socket? */
+#if !IS_ENABLED(CONFIG_BASE_SMALL)
+ /* For UDP 4-tuple hash */
+ __u16 udp_lrpa_hash;
+ struct hlist_node udp_lrpa_node;
+#endif
+
```
> It would be great if you could please share some benchmark showing the
> raw max receive PPS performances for unconnected sockets, with and
> without this series applied, to ensure this does not cause any real
> regression for such workloads.
>
Tested using sockperf tp with default msgsize (14B), 3 times for w/ and
w/o the patch set, and results show no obvious difference:
[msg/sec] test1 test2 test3 mean
w/o patch 514,664 519,040 527,115 520.3k
w/ patch 516,863 526,337 527,195 523.5k (+0.6%)
Thank you for review, Paolo.
--
Philo
next prev parent reply other threads:[~2024-10-16 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 1:29 [PATCH v4 net-next 0/3] udp: Add 4-tuple hash for connected sockets Philo Lu
2024-10-12 1:29 ` [PATCH v4 net-next 1/3] net/udp: Add a new struct for hash2 slot Philo Lu
2024-10-12 1:29 ` [PATCH v4 net-next 2/3] net/udp: Add 4-tuple hash list basis Philo Lu
2024-10-14 10:07 ` Paolo Abeni
2024-10-16 6:30 ` Philo Lu [this message]
2024-10-16 7:45 ` Paolo Abeni
2024-10-16 8:47 ` Philo Lu
2024-10-17 7:46 ` Philo Lu
2024-10-12 1:29 ` [PATCH v4 net-next 3/3] ipv4/udp: Add 4-tuple hash for connected socket Philo Lu
2024-10-14 10:19 ` Paolo Abeni
2024-10-16 7:28 ` Philo Lu
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=2888bb8f-1ee4-4342-968f-82573d583709@linux.alibaba.com \
--to=lulie@linux.alibaba.com \
--cc=antony.antony@secunet.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=fred.cc@alibaba-inc.com \
--cc=jakub@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=yubing.qiuyubing@alibaba-inc.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