[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <10A3A1C0-C20F-4A00-B450-E19868B6B720@oracle.com>
Date: Thu, 11 Sep 2025 07:36:26 +0000
From: Prakash Sangappa <prakash.sangappa@...cle.com>
To: K Prateek Nayak <kprateek.nayak@....com>
CC: Thomas Gleixner <tglx@...utronix.de>, LKML <linux-kernel@...r.kernel.org>,
Peter Zilstra <peterz@...radead.org>,
Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>,
"Paul E. McKenney" <paulmck@...nel.org>,
Boqun Feng <boqun.feng@...il.com>, Jonathan Corbet <corbet@....net>,
Madadi
Vineeth Reddy <vineethr@...ux.ibm.com>,
Steven Rostedt <rostedt@...dmis.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Arnd Bergmann
<arnd@...db.de>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>
Subject: Re: [patch 00/12] rseq: Implement time slice extension mechanism
> On Sep 11, 2025, at 5:03 AM, K Prateek Nayak <kprateek.nayak@....com> wrote:
>
> Hello Thomas,
>
> On 9/10/2025 8:20 PM, Thomas Gleixner wrote:
>> On Wed, Sep 10 2025 at 16:58, K. Prateek Nayak wrote:
>>> On 9/9/2025 4:29 AM, Thomas Gleixner wrote:
>>>> For your convenience all of it is also available as a conglomerate from
>>>> git:
>>>>
>>>> git://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git rseq/slice
>>>
>>> Apart from a couple of nit picks, I couldn't spot anything out of place
>>> and the overall approach looks solid. Please feel free to include:
>>>
>>> Reviewed-by: K Prateek Nayak <kprateek.nayak@....com>
>>
>> Thanks a lot for going through it and testing.
>>
>> Do you have a real workload or a mockup at hand, which benefits
>> from that slice extension functionality?
>
> Not at the moment but we did have some interest for this feature
> internally. Give me a week and I'll let you know if they had found a
> use-case / have a prototype to test this.
>
> In the meantime, Prakash should have a test bench that he used to
> test his early RFC
> https://lore.kernel.org/lkml/20241113000126.967713-1-prakash.sangappa@oracle.com/
>
(Have been AFK, and will be for few more days)
The above was with a database workload. Will coordinate with our database team to get it tested
with the updated API from this patch series.
Thanks,
-Prakash
> --
> Thanks and Regards,
> Prateek
>
Powered by blists - more mailing lists