On Fri, 30 Nov 2007 21:52:40 -0500 Mark Lord <[EMAIL PROTECTED]> wrote:
> Pallipadi, Venkatesh wrote: > > > > Exporting it as read only should be OK. We also need to know if > > there are hard user space dependency on writing to this from > > userspace. > .. > > Well, actually.. my scripts have a firm need to write "1" to it, > and then later restore the original value. > > This is needed to *greatly* speed up an otherwise sluggish binary I > use, just curious, but this does sound like the c-state code has a bug... independent of the sysfs thing, I think that really needs solving Can you describe the behavior a little? Or provide information to the degree that some of us can figure out how to tweak the algorithm..,. >as well as whenever I want to semi-accurately benchmark I/O. > > Is there another way to achieve exactly the same behaviour? in -mm there is.. the QoS stuff allows you to set maximum tolerable latency. If your app cant take any latency, you should set those... and the side effect is that the kernel will not do long-latency C-states or P-state transitions.. -- If you want to reach me at my work email, use [EMAIL PROTECTED] For development, discussion and tips for power savings, visit http://www.lesswatts.org - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
