On Mon, May 07, 2012 at 10:16:30PM +0530, S, Venkatraman wrote: > Mon, May 7, 2012 at 5:01 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote: > > 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 feature doesn't fiddle with the I/O scheduler's ability to balance > read vs write requests or handling requests from various process queues (CFQ). And for schedulers like no-op that don't do any read/write balancing? Also, I thought the code was queuing such demand paged requests at the front of the queues, too, so bypassing most of the read/write balancing logic of the elevators... > Also, for block devices which don't implement the ability to preempt (and even > for older versions of MMC devices which don't implement this feature), > the behaviour > falls back to waiting for write requests to complete before issuing the read. Sure, but my point is that you are adding a flag that will be set for all user data read IO, and then making it priviledged in the lower layers. > In low end flash devices, some requests might take too long than normal > due to background device maintenance (i.e flash erase / reclaim procedure) > kicking in in the context of an ongoing write, stalling them by several > orders of magnitude. And thereby stalling what might be writes critical to operation. Indeed, how does this affect the system when it starts swapping heavily? If you keep stalling writes, the system won't be able to swap and free memory... > This implementation (See 14/16) does have several checks and > timers to see that it's not triggered very often. In my tests, > where I usually have a generous preemption time window, the abort > happens < 0.1% of the time. Yes, but seeing as the user has direct control of the pre-emption vector, it's not hard to imagine someone using it for a timing attack... > > 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.... > > Indeed, the feature is built mostly in the low level device driver and > minor changes in the elevator. Changes above the block layer are only > about setting > attributes and transparent to their operation. The problem is that the attribute you are setting covers every single data read that is done by all users. If that's what you want to have happen, then why do you even need a new flag at this layer? Just treat every non-REQ_META read request as a demand paged IO and you've got exactly the same behaviour without needing to tag at the higher layer.... 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
