From: Thomas Gleixner <tglx@linutronix.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 06/11] futex: Allow to re-allocate the private hash bucket.
Date: Wed, 11 Dec 2024 16:22:58 +0100 [thread overview]
Message-ID: <87jzc6b5wt.ffs@tglx> (raw)
In-Reply-To: <8734ivcgx7.ffs@tglx>
On Tue, Dec 10 2024 at 23:27, Thomas Gleixner wrote:
> On Tue, Dec 03 2024 at 17:42, Sebastian Andrzej Siewior wrote:
> realloc_or_restore_hash()
swap_hash()
{
old_hash = current->mm->futex.hash;
new_hash = current->mm->futex.new_hash;
rehash(new_hash, old_hash);
rcu_assign_pointer(current->mm->futex.hash, new_hash);
rcu_free(old_hash);
}
> rehash(new_hash, old_hash)
> {
> // old_hash is marked dead, so new waiters cannot queue
> // themself and are stuck on the hash_mutex.
>
> for (i = 0; i < old_hash->size; i++) {
> hb1 = &old_hash->queues[i];
>
> // Protect the old bucket against unqueue(), as it does
> // not try to get a reference on the hash bucket. It
> // solely relies on q->lock_ptr.
> spin_lock(&hb1->lock);
>
> plist_for_each_entry_safe(q, tmp, hb1, list) {
> hb2 = hash_bucket(new_hash, &q->key);
> // Nesting is safe as this is a one time operation
> spin_lock_nested(&hb2->lock);
>
> plist_del(&q->list, &hb->chain);
>
> // Redirect the lock pointer to the new hash
> // bucket. See unqueue().
> q->lock_ptr = &hb2->lock;
>
> plist_add(&q->list, &hb->chain);
> }
> }
> }
>
> fork()
> {
> if (hash_needs_resize())
> hash_putref(mm->futex.hash);
futex_validate_hash();
futex_validate_hash()
{
guard(mutex)();
if (!hash_needs_resize(mm->futex.hash))
return;
if (mm->futex.new_hash && !hash_needs_resize(mm->futex.new_hash))
return;
new = alloc();
if (!new)
return;
current->mm.futex_new_hash = new;
if (!rcuput_ref(mm->futex.hash->ref))
return;
swap_hash();
}
next prev parent reply other threads:[~2024-12-11 15:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 16:42 [PATCH v4 0/11] futex: Add support task local hash maps Sebastian Andrzej Siewior
2024-12-03 16:42 ` [PATCH v4 01/11] futex: Create helper function to initialize a hash slot Sebastian Andrzej Siewior
2024-12-10 15:13 ` Thomas Gleixner
2024-12-03 16:42 ` [PATCH v4 02/11] futex: Add basic infrastructure for local task local hash Sebastian Andrzej Siewior
2024-12-10 15:23 ` Thomas Gleixner
2024-12-03 16:42 ` [PATCH v4 03/11] futex: Allow automatic allocation of process wide futex hash Sebastian Andrzej Siewior
2024-12-10 16:07 ` Thomas Gleixner
2024-12-03 16:42 ` [PATCH v4 04/11] futex: Hash only the address for private futexes Sebastian Andrzej Siewior
2024-12-03 16:42 ` [PATCH v4 05/11] futex: Track the futex hash bucket Sebastian Andrzej Siewior
2024-12-10 18:45 ` Thomas Gleixner
2024-12-12 16:41 ` Sebastian Andrzej Siewior
2024-12-03 16:42 ` [PATCH v4 06/11] futex: Allow to re-allocate the private " Sebastian Andrzej Siewior
2024-12-10 22:27 ` Thomas Gleixner
2024-12-11 14:32 ` Thomas Gleixner
2024-12-11 15:22 ` Thomas Gleixner [this message]
2024-12-12 16:16 ` Sebastian Andrzej Siewior
2024-12-03 16:42 ` [PATCH v4 07/11] futex: Allow to make the number of slots invariant Sebastian Andrzej Siewior
2024-12-06 8:19 ` Sebastian Andrzej Siewior
2024-12-03 16:42 ` [PATCH v4 08/11] futex: Resize futex hash table based on number of threads Sebastian Andrzej Siewior
2024-12-06 9:27 ` Thomas Gleixner
2024-12-03 16:42 ` [PATCH v4 09/11] tools/perf: Add the prctl(PR_FUTEX_HASH,…) to futex-hash Sebastian Andrzej Siewior
2024-12-03 16:42 ` [PATCH v4 10/11] tools/perf: The the current affinity for CPU pinning in futex-hash Sebastian Andrzej Siewior
2024-12-03 16:42 ` [PATCH v4 11/11] tools/perf: Allocate futex locks on the local CPU-node Sebastian Andrzej Siewior
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=87jzc6b5wt.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.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