Re: status of Preemptible Kernel 2.6.7

[Timothy Miller]

Robert Love wrote:
> On Wed, 2004-06-23 at 15:30 -0400, Timothy Miller wrote:
>
>
> > I wasn't talking about locks.  I was talking about kernel functions 
> > taking long periods of time, cases where preempt has been useful to 
> > reduce kernel latency.
> >
> > Holding locks for extended periods is something else entirely.
>
>
> I know what you were talking about.  I was replying that it seems better
> overall to me if we work to eliminate long lock hold times (which then
> eliminates long non-preemption times) than litter the kernel with
> explicit rescheduling statements.

Yes, getting rid of locks does seem to be a more immediately productive 
thing to do.

Are there any cases where we claim locks on data, rather than metadata? 
 That is to say, one would prefer to lock, claim a pointer or reference 
or such, and then unlock, rather than to lock, manipulate data, and then 
unlock, right?

There might be situations where the data structures involved are larger 
(more pointers, flags, etc.), but we can get control of data without 
having to hold a lock on it.

Am I making sense?  :)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/