[lkml]   [2000]   [Sep]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Drivers that potentially leave state as TASK_{UN}INTERRUPTIBLE
Date said:
> So it seems to be a bug at least in terms of timing. Unfortunately I
> only got about 4 replies to the patches that touched 20+ drivers. I
> suppose I should just hassle maintainers until they fix it or tell me
> where I've gone wrong ...

Actually, I was quite happy calling schedule_timeout in the flash drivers
without changing current->state. I'm waiting to something to happen, and
just to be considerate, I'm asking to be put to sleep for the 'expected'
amount of time for whatever's happening. If there's other stuff on the run
queue, it won't return immediately, will it? If there isn't other stuff on
the run queue, I'll just busy wait till the flash chip's finished.

Otherwise, it would be TASK_UNINTERRUPTIBLE.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.049 / U:0.040 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site