From: Reinette Chatre <reinette.chatre@intel.com>
To: Peter Newman <peternewman@google.com>, <fenghua.yu@intel.com>
Cc: <Babu.Moger@amd.com>, <bp@alien8.de>,
<dave.hansen@linux.intel.com>, <eranian@google.com>,
<gupasani@google.com>, <hpa@zytor.com>, <james.morse@arm.com>,
<linux-kernel@vger.kernel.org>, <mingo@redhat.com>,
<skodak@google.com>, <tglx@linutronix.de>, <tony.luck@intel.com>,
<x86@kernel.org>
Subject: Re: [PATCH v4 1/3] x86/resctrl: Factor rdtgroup lock for multi-file ops
Date: Thu, 23 Mar 2023 10:58:14 -0700 [thread overview]
Message-ID: <ce57dcbb-5464-3340-34d0-af1e3f191b85@intel.com> (raw)
In-Reply-To: <20230308131452.383914-2-peternewman@google.com>
Hi Peter,
On 3/8/2023 5:14 AM, Peter Newman wrote:
> rdtgroup_kn_lock_live() can only release a kernfs reference for a single
> file before waiting on the rdtgroup_mutex, limiting its usefulness for
> operations on multiple files, such as rename.
>
> Factor the work needed to respectively break and unbreak active
> protection on an individual file into rdtgroup_kn_{get,put}().
>
> No functional change.
>
> Signed-off-by: Peter Newman <peternewman@google.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Reinette
next prev parent reply other threads:[~2023-03-23 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 13:14 [PATCH v4 0/3] Subject: x86/resctrl: Implement rename to help move containers' tasks Peter Newman
2023-03-08 13:14 ` [PATCH v4 1/3] x86/resctrl: Factor rdtgroup lock for multi-file ops Peter Newman
2023-03-23 17:58 ` Reinette Chatre [this message]
2023-03-08 13:14 ` [PATCH v4 2/3] x86/resctrl: Parameterize rdt_move_group_tasks() task matching Peter Newman
2023-03-23 18:02 ` Reinette Chatre
2023-03-30 12:50 ` Peter Newman
2023-03-08 13:14 ` [PATCH v4 3/3] x86/resctrl: Implement rename op for mon groups Peter Newman
2023-03-23 18:08 ` Reinette Chatre
2023-03-30 13:43 ` Peter Newman
2023-04-03 18:21 ` Reinette Chatre
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=ce57dcbb-5464-3340-34d0-af1e3f191b85@intel.com \
--to=reinette.chatre@intel.com \
--cc=Babu.Moger@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=gupasani@google.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peternewman@google.com \
--cc=skodak@google.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@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
all inboxes | Powered by JetHome®