The general idea: A daemon running in user space monitors input data
from an accelerometer. When the daemon detects a critical condition,
That sounds like a non starter. What if the box is busy, what if the
daemon or something you touch needs memory and causes paging ?
Given the accelerometer
Hi all,
at the moment I'm having another go at trying to make the disk shock
protection patch fit for upstream submission. However, there are still
some fundamental issues I'd like to discuss in order to make sure that
I'm heading in the right direction.
The general idea: A daemon running in
Elias Oltmanns wrote:
The general idea: A daemon running in user space monitors input data
from an accelerometer. When the daemon detects a critical condition,
i.e., a sudden acceleration (for instance, laptop slides off the desk),
it signals the kernel so the hard disk may be put into a (more)
Jeff Garzik [EMAIL PROTECTED] wrote:
Elias Oltmanns wrote:
The general idea: A daemon running in user space monitors input data
from an accelerometer. When the daemon detects a critical condition,
i.e., a sudden acceleration (for instance, laptop slides off the desk),
it signals the kernel so
On Tue, 26 Feb 2008, Elias Oltmanns wrote:
You don't want, for example, to swap out other apps, swap in the
daemon, in order to handle a sudden acceleration.
Quite. But with mlock this particular problem can be handled in user
space just fine. The only reason I can see right now for
