On Mon, 19 Feb 2001, Marcelo Tosatti wrote: > > The following patch makes lock_buffer() use the exclusive wakeup scheme > added in 2.3. Ugh, This is horrible. You should NOT have one function that does two completely different things depending on a flag. That way lies madness and bad coding habits. Just do two different functions - make one be "__wait_on_buffer()", and the other be "__lock_buffer()". See how the page functions work. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: [PATCH] exclusive wakeup for lock_bufferMarcelo Tosatti <marcelo _at_ conectiva.com.br>
- [PATCH] exclusive wakeup for lock_bufferMarcelo Tosatti <marcelo _at_ conectiva.com.br>
- Prev by Date: [PATCH] exclusive wakeup for lock_buffer
- Next by Date: Re: problems with reiserfs + nfs using 2.4.2-pre4
- Prev by thread: [PATCH] exclusive wakeup for lock_buffer
- Next by thread: Re: [PATCH] exclusive wakeup for lock_buffer
- Indexes:[Main][Thread]