[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101124100242.GW19571@csn.ul.ie>
Date: Wed, 24 Nov 2010 10:02:42 +0000
From: Mel Gorman <mel@....ul.ie>
To: Minchan Kim <minchan.kim@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-mm <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Rik van Riel <riel@...hat.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Johannes Weiner <hannes@...xchg.org>,
Nick Piggin <npiggin@...nel.dk>
Subject: Re: [RFC 1/2] deactive invalidated pages
On Wed, Nov 24, 2010 at 08:24:35AM +0900, Minchan Kim wrote:
> >> <SNIP>
> >>
> >> +static void __pagevec_lru_deactive(struct pagevec *pvec)
> >> +{
> >
> > Might be worth commenting that this function must be called with pre-emption
> > disabled. FWIW, I am reasonably sure your implementation is prefectly safe
> > but a note wouldn't hurt.
>
> Will fix.
>
Thanks
> >
> >> + int i, lru, file;
> >> +
> >> + struct zone *zone = NULL;
> >> +
> >> + for (i = 0; i < pagevec_count(pvec); i++) {
> >> + struct page *page = pvec->pages[i];
> >> + struct zone *pagezone = page_zone(page);
> >> +
> >> + if (pagezone != zone) {
> >> + if (zone)
> >> + spin_unlock_irq(&zone->lru_lock);
> >> + zone = pagezone;
> >> + spin_lock_irq(&zone->lru_lock);
> >> + }
> >> +
> >> + if (PageLRU(page)) {
> >> + if (PageActive(page)) {
> >> + file = page_is_file_cache(page);
> >> + lru = page_lru_base_type(page);
> >> + del_page_from_lru_list(zone, page,
> >> + lru + LRU_ACTIVE);
> >> + ClearPageActive(page);
> >> + ClearPageReferenced(page);
> >> + add_page_to_lru_list(zone, page, lru);
> >> + __count_vm_event(PGDEACTIVATE);
> >> +
> >
> > What about memcg, do we not need to be calling mem_cgroup_add_lru_list() here
> > as well? I'm looking at the differences between what move_active_pages_to_lru()
>
> Recently, add_page_to_lru_list contains mem_cgroup_add_lru_list.
>
My bad, you're right. I was thrown by move_active_pages_to_lru() needing to
do memcg stuff manually and didn't spot why it ok to miss it here.
> > is doing and this. I'm wondering if it'd be worth your whole building a list
> > of active pages that are to be moved to the inactive list and passing them
> > to move_active_pages_to_lru() ? I confuess I have not thought about it deeply
> > so it might be a terrible suggestion but it might reduce duplication of code.
>
> Firstly I tried it so I sent a patch about making
> move_to_active_pages_to_lru more generic.
> move_to_active_pages_to_lru needs zone argument so I need gathering
> pages per zone in truncate.
> I don't want for user of the function to consider even zone and
> zone->lru_lock handling.
>
> I think the lru_demote_pages could be used elsewhere(ex, readahead max
> size heuristic).
> So it's generic and easy to use. :)
>
Ok, that's fair enough.
> >
> >> + update_page_reclaim_stat(zone, page, file, 0);
> >> + }
> >> + }
> >> + }
> >> + if (zone)
> >> + spin_unlock_irq(&zone->lru_lock);
> >> +
> >> + release_pages(pvec->pages, pvec->nr, pvec->cold);
> >> + pagevec_reinit(pvec);
> >> +}
> >> +
> >> /*
> >> * Drain pages out of the cpu's pagevecs.
> >> * Either "cpu" is the current CPU, and preemption has already been
> >> @@ -292,8 +333,28 @@ static void drain_cpu_pagevecs(int cpu)
> >> pagevec_move_tail(pvec);
> >> local_irq_restore(flags);
> >> }
> >> +
> >> + pvec = &per_cpu(lru_deactive_pvecs, cpu);
> >> + if (pagevec_count(pvec))
> >> + __pagevec_lru_deactive(pvec);
> >> +}
> >> +
> >> +/*
> >> + * Function used to forecefully demote a page to the head of the inactive
> >> + * list.
> >
> > s/forecefully/forcefully/
> >
> > The comment should also state *why* and under what circumstances we move
> > pages to the inactive list like this. Also based on the discussions
> > elsewhere in this thread, it'd be nice to include a comment why it's the
> > head of the inactive list and not the tail.
>
> Fair enough.
>
> Thanks for the comment, Mel.
>
> --
> Kind regards,
> Minchan Kim
>
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists