On Fri, 11 Feb 2000, Peter Rival wrote:
>Andrea Arcangeli wrote:
>
>> On Fri, 11 Feb 2000, Bruce Thompson wrote:
>>
>> >process. Once the counter exceeds some particular highwater mark the
>> >process is blocked from entering more requests until the counter
>> >drops to some lowwater mark. Hmm. ANother thought. Make the counter
>>
>> You never generate I/O from tasks. It's when the buffer is too old that
>> kupdate flushes writes to disk. At that time the process is just exited
>> and the user just run another program that gets stalled due the write
>> flood.
>>
>
>I believe this is technically incorrect - what about fsync() calls and files
Yes, I was generalizing in speach-mode to bias my words (it's been a fast
reply), and my only object was to comment on the per-task information that
become meaningless with async write I/O (that's the common case).
>opened O_SYNC? I'm sick, so feel free to shoot me if I'm off-base. ;)
You are completly correct, also rawio, mount -o sync, `/bin/sync` etc..
all cause write requests to be queued into the elevator from the task
context.
Thanks for pointing this out and sorry if I am been confusing.
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Feb 15 2000 - 21:00:21 EST