[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <your-ad-here.call-01625750365-ext-6037@work.hours>
Date: Thu, 8 Jul 2021 15:19:25 +0200
From: Vasily Gorbik <gor@...ux.ibm.com>
To: Petr Mladek <pmladek@...e.com>
Cc: Josh Poimboeuf <jpoimboe@...hat.com>,
Jiri Kosina <jikos@...nel.org>,
Miroslav Benes <mbenes@...e.cz>,
Joe Lawrence <joe.lawrence@...hat.com>,
Heiko Carstens <hca@...ux.ibm.com>,
Sven Schnelle <svens@...ux.ibm.com>,
Sumanth Korikkar <sumanthk@...ux.ibm.com>,
live-patching@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] livepatch: Speed up transition retries
On Thu, Jul 08, 2021 at 12:35:24PM +0200, Petr Mladek wrote:
> On Wed 2021-07-07 14:49:41, Vasily Gorbik wrote:
> > That's just a racy hack for now for demonstration purposes.
> >
> > For s390 LPAR with 128 cpu this reduces livepatch kselftest run time
> > from
> > real 1m11.837s
> > user 0m0.603s
> > sys 0m10.940s
> >
> > to
> > real 0m14.550s
> > user 0m0.420s
> > sys 0m5.779s
> >
> > Would smth like that be useful for production use cases?
> > Any ideas how to approach that more gracefully?
>
> Honestly, I do not see a real life use case for this, except maybe
> speeding up a test suite.
>
> The livepatch transition is more about reliability than about speed.
> In the real life, a livepatch will be applied only once in a while.
That's what I thought. Thanks for looking. Dropping this one.
Powered by blists - more mailing lists