From: Reinette Chatre <reinette.chatre@intel.com>
To: "Shaopeng Tan (Fujitsu)" <tan.shaopeng@fujitsu.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: James Morse <james.morse@arm.com>,
Yury Norov <yury.norov@gmail.com>,
"Dave Martin" <dave.martin@arm.com>,
"fenghuay@nvidia.com" <fenghuay@nvidia.com>,
"peternewman@google.com" <peternewman@google.com>,
Babu Moger <Babu.Moger@amd.com>, Borislav Petkov <bp@alien8.de>,
"shameerali.kolothum.thodi@huawei.com"
<shameerali.kolothum.thodi@huawei.com>,
"bobo.shaobowang@huawei.com" <bobo.shaobowang@huawei.com>,
D Scott Phillips OS <scott@os.amperecomputing.com>,
"carl@os.amperecomputing.com" <carl@os.amperecomputing.com>,
Shanker Donthineni <sdonthineni@nvidia.com>,
Xin Hao <xhao@linux.alibaba.com>,
"baolin.wang@linux.alibaba.com" <baolin.wang@linux.alibaba.com>,
"lcherian@marvell.com" <lcherian@marvell.com>,
"amitsinght@marvell.com" <amitsinght@marvell.com>,
Ingo Molnar <mingo@redhat.com>,
David Hildenbrand <david@redhat.com>,
"H Peter Anvin" <hpa@zytor.com>,
Rex Nie <rex.nie@jaguarmicro.com>,
Jamie Iles <quic_jiles@quicinc.com>,
"dfustini@baylibre.com" <dfustini@baylibre.com>,
Thomas Gleixner <tglx@linutronix.de>,
'Koba Ko' <kobak@nvidia.com>
Subject: Re: [PATCH v2] fs/resctrl: Optimize code in rdt_get_tree()
Date: Fri, 18 Jul 2025 08:48:57 -0700 [thread overview]
Message-ID: <34924bd1-8070-4ecb-8696-c4a575c710c8@intel.com> (raw)
In-Reply-To: <OSZPR01MB87985042129BAD34812742F48B50A@OSZPR01MB8798.jpnprd01.prod.outlook.com>
Hi Shaopeng,
On 7/17/25 10:55 PM, Shaopeng Tan (Fujitsu) wrote:
> Hello Reinette,
>
> Do you have any other comments?
>
No other comments from my side. I expect that you are wondering why this
has not been merged yet. It does take some effort from multiple folks to
get a patch upstream. At this time this is the only pending resctrl change
that is ready for inclusion via tip. When I considered its impact on
resctrl together with effort to get it merged I decided to hold it back
to be included with other resctrl changes that are being polished at the
moment. Please let me know if I missed something and this work should
actually be handled with more urgency.
Reinette
next prev parent reply other threads:[~2025-07-18 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250623073154.3320458-1-tan.shaopeng@jp.fujitsu.com>
2025-07-18 5:55 ` Shaopeng Tan (Fujitsu)
2025-07-18 15:48 ` Reinette Chatre [this message]
2025-06-23 7:50 Shaopeng Tan
2025-06-24 3:51 ` Koba Ko
2025-07-18 5:54 ` Shaopeng Tan (Fujitsu)
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=34924bd1-8070-4ecb-8696-c4a575c710c8@intel.com \
--to=reinette.chatre@intel.com \
--cc=Babu.Moger@amd.com \
--cc=amitsinght@marvell.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=bobo.shaobowang@huawei.com \
--cc=bp@alien8.de \
--cc=carl@os.amperecomputing.com \
--cc=dave.martin@arm.com \
--cc=david@redhat.com \
--cc=dfustini@baylibre.com \
--cc=fenghuay@nvidia.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=kobak@nvidia.com \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peternewman@google.com \
--cc=quic_jiles@quicinc.com \
--cc=rex.nie@jaguarmicro.com \
--cc=scott@os.amperecomputing.com \
--cc=sdonthineni@nvidia.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=tan.shaopeng@fujitsu.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xhao@linux.alibaba.com \
--cc=yury.norov@gmail.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
all inboxes | Powered by JetHome®