From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <gnaaman@drivenets.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<kuniyu@amazon.com>, <netdev@vger.kernel.org>,
<pabeni@redhat.com>
Subject: Re: [PATCH net-next v4 1/6] Add hlist_node to struct neighbour
Date: Tue, 15 Oct 2024 15:49:58 -0700 [thread overview]
Message-ID: <20241015224958.64713-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20241015165929.3203216-2-gnaaman@drivenets.com>
From: Gilad Naaman <gnaaman@drivenets.com>
Date: Tue, 15 Oct 2024 16:59:21 +0000
> @@ -531,7 +533,9 @@ static void neigh_get_hash_rnd(u32 *x)
> static struct neigh_hash_table *neigh_hash_alloc(unsigned int shift)
> {
> size_t size = (1 << shift) * sizeof(struct neighbour *);
> + size_t hash_heads_size = (1 << shift) * sizeof(struct hlist_head);
> struct neigh_hash_table *ret;
> + struct hlist_head *hash_heads;
> struct neighbour __rcu **buckets;
> int i;
nit:
While at it, please sort variables in reverse xmas tree order.
Same for other places.
https://docs.kernel.org/process/maintainer-netdev.html#local-variable-ordering-reverse-xmas-tree-rcs
>
> @@ -540,17 +544,28 @@ static struct neigh_hash_table *neigh_hash_alloc(unsigned int shift)
> return NULL;
> if (size <= PAGE_SIZE) {
> buckets = kzalloc(size, GFP_ATOMIC);
> + hash_heads = kzalloc(hash_heads_size, GFP_ATOMIC);
> + if (!hash_heads)
> + kfree(buckets);
> } else {
> buckets = (struct neighbour __rcu **)
> __get_free_pages(GFP_ATOMIC | __GFP_ZERO,
> get_order(size));
> kmemleak_alloc(buckets, size, 1, GFP_ATOMIC);
> +
> + hash_heads = (struct hlist_head *)
> + __get_free_pages(GFP_ATOMIC | __GFP_ZERO,
> + get_order(hash_heads_size));
> + kmemleak_alloc(hash_heads, hash_heads_size, 1, GFP_ATOMIC);
> + if (!hash_heads)
> + free_pages((unsigned long)buckets, get_order(size));
> }
> - if (!buckets) {
> + if (!buckets || !hash_heads) {
> kfree(ret);
> return NULL;
If buckets is NULL and hash_heads isn't, hash_heads is leaked.
> }
> ret->hash_buckets = buckets;
> + ret->hash_heads = hash_heads;
> ret->hash_shift = shift;
> for (i = 0; i < NEIGH_NUM_HASH_RND; i++)
> neigh_get_hash_rnd(&ret->hash_rnd[i]);
next prev parent reply other threads:[~2024-10-15 22:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 16:59 [PATCH net-next v4 0/6] Improve neigh_flush_dev performance Gilad Naaman
2024-10-15 16:59 ` [PATCH net-next v4 1/6] Add hlist_node to struct neighbour Gilad Naaman
2024-10-15 22:49 ` Kuniyuki Iwashima [this message]
2024-10-15 16:59 ` [PATCH net-next v4 2/6] Define neigh_for_each Gilad Naaman
2024-10-15 22:57 ` Kuniyuki Iwashima
2024-10-15 16:59 ` [PATCH net-next v4 3/6] Convert neigh_* seq_file functions to use hlist Gilad Naaman
2024-10-15 23:25 ` Kuniyuki Iwashima
2024-10-16 9:11 ` Gilad Naaman
2024-10-16 20:54 ` Kuniyuki Iwashima
2024-10-17 6:31 ` Gilad Naaman
2024-10-15 16:59 ` [PATCH net-next v4 4/6] Convert neighbour iteration to use hlist+macro Gilad Naaman
2024-10-15 23:38 ` Kuniyuki Iwashima
2024-10-16 9:18 ` Gilad Naaman
2024-10-15 16:59 ` [PATCH net-next v4 5/6] Remove bare neighbour::next pointer Gilad Naaman
2024-10-15 16:59 ` [PATCH net-next v4 6/6] Create netdev->neighbour association Gilad Naaman
2024-10-15 23:54 ` Kuniyuki Iwashima
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=20241015224958.64713-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnaaman@drivenets.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).