[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0804251009340.2779@woody.linux-foundation.org>
Date: Fri, 25 Apr 2008 10:13:29 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Ingo Molnar <mingo@...e.hu>
cc: Andi Kleen <andi@...stfloor.org>, Jiri Slaby <jirislaby@...il.com>,
David Miller <davem@...emloft.net>, zdenek.kabelac@...il.com,
rjw@...k.pl, paulmck@...ux.vnet.ibm.com, akpm@...ux-foundation.org,
linux-ext4@...r.kernel.org, herbert@...dor.apana.org.au,
penberg@...helsinki.fi, clameter@....com,
linux-kernel@...r.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
pageexec@...email.hu, "H. Peter Anvin" <hpa@...or.com>,
Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: [PATCH 1/1] x86: fix text_poke
On Fri, 25 Apr 2008, Ingo Molnar wrote:
>
> performance i dont think we should be too worried about at this moment -
> this code is so rarely used that it should be driven by robustness i
> think.
That really isn't true. This isn't done just once. It's done many
thousands of times.
I agree that it has to be robust, but if we want to make suspend/resume
be instantaneous (and we do), performance does actually matter. Yes, this
is probably much less of a problem than waiting for devices, and no, I
haven't timed it, but if I counted right, we'll literally be going almost
ten thousand of these calls over a suspend/resume cycle.
That's not "rarely used".
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists