On Thu, May 03, 2012 at 07:53:00PM +0530, Venkatraman S wrote: > From: Ilan Smith <ilan.smith@xxxxxxxxxxx> > > Add attribute to identify demand paging requests. > Mark readpages with demand paging attribute. > > Signed-off-by: Ilan Smith <ilan.smith@xxxxxxxxxxx> > Signed-off-by: Alex Lemberg <alex.lemberg@xxxxxxxxxxx> > Signed-off-by: Venkatraman S <svenkatr@xxxxxx> > --- > fs/mpage.c | 2 ++ > include/linux/bio.h | 7 +++++++ > include/linux/blk_types.h | 2 ++ > 3 files changed, 11 insertions(+) > > diff --git a/fs/mpage.c b/fs/mpage.c > index 0face1c..8b144f5 100644 > --- a/fs/mpage.c > +++ b/fs/mpage.c > @@ -386,6 +386,8 @@ mpage_readpages(struct address_space *mapping, struct list_head *pages, > &last_block_in_bio, &map_bh, > &first_logical_block, > get_block); > + if (bio) > + bio->bi_rw |= REQ_RW_DMPG; Have you thought about the potential for DOSing a machine with this? That is, user data reads can now preempt writes of any kind, effectively stalling writeback and memory reclaim which will lead to OOM situations. Or, alternatively, journal flushing will get stalled and no new modifications can take place until the read stream stops. This really seems like functionality that belongs in an IO scheduler so that write starvation can be avoided, not in high-level data read paths where we have no clue about anything else going on in the IO subsystem.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
