[lkml]   [2004]   [Mar]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.4-mm2
Andrew Morton <> wrote:
> Andrew Morton <> wrote:
> >
> > I'm thinking that the right thing to do here is to change submit_bh()
> > callers and ll_rw_block() to run set_page_writeback(bh->b_page) when they
> > start the buffer writeout and to do the run-around-the-buffer_heads thing
> > at I/O completion.
> A page may have a mix of writeback and dirty+non-writeback buffers. It
> appears that the page-level writeback code will handle this correctly. But
> it requires that the page lock be held when we run set_page_writeback(), so
> that tears that. hmm.

I'll work this out yet.

We change the PageWriteback() predicate to go in and see if any of the
buffer_heads are under I/O too. And we change wait_on_page_writeback() to
also wait on any buffer_heads.

That means two new silly address_space ops. Or a new page flag which means
"the thing at ->private is buffer_heads". Probably the latter.

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 14:01    [W:0.163 / U:2.800 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site