From: Eric Chanudet <echanude@redhat.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Larsson <alexl@redhat.com>,
Andrew Halaney <ahalaney@redhat.com>
Subject: Re: [RFC PATCH 0/1] fs/namespace: defer free_mount from namespace_unlock
Date: Thu, 19 Jan 2023 16:14:14 -0500 [thread overview]
Message-ID: <20230119211414.qfkh3hrmupcynrrb@echanude> (raw)
In-Reply-To: <20230119205521.497401-1-echanude@redhat.com>
On Thu, Jan 19, 2023 at 03:55:20PM -0500, Eric Chanudet wrote:
> We noticed a significant slow down when running a containers on an
> Aarch64 system with the RT patch set using the following test:
> [...]
> With the following patch, namespace_unlock will queue up the resources
> that needs to be released and defer the operation through call_rcu to
> return without waiting for the grace period.
I did not CC:linux-rt-users. Resending with them included, my apologies.
--
Eric Chanudet
prev parent reply other threads:[~2023-01-19 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 20:55 Eric Chanudet
2023-01-19 20:55 ` [RFC PATCH 1/1] " Eric Chanudet
2023-01-19 22:03 ` Al Viro
2023-01-19 21:14 ` Eric Chanudet [this message]
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=20230119211414.qfkh3hrmupcynrrb@echanude \
--to=echanude@redhat.com \
--cc=ahalaney@redhat.com \
--cc=alexl@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®