[lkml]   [2003]   [Jan]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.5.59-mm5
>>>>> Andrew Morton (AM) writes:

AM> That's correct. Reads are usually synchronous and writes are
AM> rarely synchronous.

AM> The most common place where the kernel forces a user process to
AM> wait on completion of a write is actually in unlink (truncate,
AM> really). Because truncate must wait for in-progress I/O to
AM> complete before allowing the filesystem to free (and potentially
AM> reuse) the affected blocks.

looks like I miss something here.

why do wait for write completion in truncate?

getblk (blockmap);
getblk (bitmap);
set 0 in blockmap->b_data[N];
mark_buffer_dirty (blockmap);
clear_bit (N, &bitmap);
mark_buffer_dirty (bitmap);

isn't that enough?

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

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