mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Rik van Riel <riel@redhat.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Nick Piggin <npiggin@kernel.dk>
Subject: Re: [RFC 1/2] deactive invalidated pages
Date: Tue, 23 Nov 2010 17:01:14 +0900 (JST)	[thread overview]
Message-ID: <20101123165240.7BC2.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <AANLkTinZmv540r+EkjwUu6cd9c1u7qG9iR+pvp3YqZC1@mail.gmail.com>

> Hi KOSAKI,
> 
> 2010/11/23 KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>:
> >> By Other approach, app developer uses POSIX_FADV_DONTNEED.
> >> But it has a problem. If kernel meets page is writing
> >> during invalidate_mapping_pages, it can't work.
> >> It is very hard for application programmer to use it.
> >> Because they always have to sync data before calling
> >> fadivse(..POSIX_FADV_DONTNEED) to make sure the pages could
> >> be discardable. At last, they can't use deferred write of kernel
> >> so that they could see performance loss.
> >> (http://insights.oetiker.ch/linux/fadvise.html)
> >
> > If rsync use the above url patch, we don't need your patch.
> > fdatasync() + POSIX_FADV_DONTNEED should work fine.
> 
> It works well. But it needs always fdatasync before calling fadvise.
> For small file, it hurt performance since we can't use the deferred write.

I doubt rsync need to call fdatasync. Why?

If rsync continue to do following loop, some POSIX_FADV_DONTNEED
may not drop some dirty pages. But they can be dropped at next loop's
POSIX_FADV_DONTNEED. Then, It doesn't make serious issue.

1) read
2) write
3) POSIX_FADV_DONTNEED
4) goto 1


Am I missing anything?


> > So, I think the core worth of previous PeterZ's patch is in readahead
> > based heuristics. I'm curious why you drop it.
> >
> 
> In previous peter's patch, it couldn't move active page into inactive list.
> So it's not what i want and I think invalidation is stronger hint than
> the readahead heuristic.
> But if we need it, I will add it in my series. It can help reclaiming
> unnecessary inactive page asap.
> but before that, I hope we make sure fadvise works well enough.

I've got it.Yeah, 1) implement manual  oepration 2) add automatic heuristic 
is right order. I think. we can easily test your one.



> >> In fact, invalidate is very big hint to reclaimer.
> >> It means we don't use the page any more. So let's move
> >> the writing page into inactive list's head.
> >
> > But, I agree this.
> 
> Thank you.
>
> >> +static void __pagevec_lru_deactive(struct pagevec *pvec)
> >> +{
> >> +     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);
> >> +
> >> +                             update_page_reclaim_stat(zone, page, file, 0);
> >
> > When PageActive is unset, we need to change cgroup lru too.
> 
> Doesn't add_page_to_lru_list/del_page_from_lru_list do it?

Grr, my fault. I've forgot to we changed add_page_to_lru_list. 




  parent reply	other threads:[~2010-11-23  8:01 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21 14:30 Minchan Kim
2010-11-21 14:30 ` [RFC 2/2] Prevent promotion of page in madvise_dontneed Minchan Kim
2010-11-21 14:38   ` Minchan Kim
2010-11-21 16:34   ` Ben Gamari
2010-11-22  0:31     ` Minchan Kim
2010-11-22 22:21   ` Andrew Morton
2010-11-23  4:57     ` Minchan Kim
2010-11-23  9:50     ` Mel Gorman
2010-11-23 23:49       ` Minchan Kim
2010-11-21 15:21 ` [RFC 1/2] deactive invalidated pages Ben Gamari
2010-11-23  7:16   ` KOSAKI Motohiro
2010-11-23 13:48     ` Ben Gamari
2010-11-23 23:48       ` Minchan Kim
2010-11-23 14:49     ` [RFC PATCH] fadvise support in rsync Ben Gamari
2010-11-23 15:35       ` Pádraig Brady
2010-11-24  0:17       ` KOSAKI Motohiro
2010-11-23 14:49     ` [PATCH 1/3] Add fadvise interface wrapper Ben Gamari
2010-11-23 14:49     ` [PATCH 2/3] Inform kernel of FADV_DONTNEED hint in sender Ben Gamari
2010-11-23 14:49     ` [PATCH 3/3] Inform kernel of FADV_DONTNEED hint in receiver Ben Gamari
2010-11-22  1:17 ` [RFC 1/2] deactive invalidated pages Rik van Riel
2010-11-22 22:14 ` Andrew Morton
2010-11-23  4:52   ` Minchan Kim
2010-11-23  5:01     ` Andrew Morton
2010-11-23  5:23       ` Minchan Kim
2010-11-23  5:22         ` Andrew Morton
2010-11-23  5:45           ` Minchan Kim
2010-11-23  5:48             ` Andrew Morton
2010-11-23  6:05               ` Minchan Kim
2010-11-23  7:15                 ` Andrew Morton
2010-11-23  7:44                   ` Minchan Kim
2010-11-23  7:53                     ` Andrew Morton
2010-11-23  8:02                       ` Minchan Kim
2010-11-23  9:43               ` Mel Gorman
2010-11-23 23:32                 ` Minchan Kim
2010-11-23  9:38       ` Mel Gorman
2010-11-23 14:55         ` Ben Gamari
2010-11-23 14:58           ` Mel Gorman
2010-11-23 20:35             ` Andrew Morton
2010-11-23 22:10               ` Mel Gorman
2010-11-23 23:45                 ` Minchan Kim
2010-11-24 18:01                   ` Mel Gorman
2010-11-23  7:16 ` KOSAKI Motohiro
2010-11-23  7:40   ` Minchan Kim
2010-11-23  7:42     ` Andrew Morton
2010-11-23  8:01     ` KOSAKI Motohiro [this message]
2010-11-23  8:44       ` Minchan Kim
2010-11-23  9:02         ` KOSAKI Motohiro
2010-11-23  9:05           ` Minchan Kim
2010-11-23  9:07             ` Minchan Kim
2010-11-23 14:57   ` Ben Gamari
2010-11-24  0:13     ` KOSAKI Motohiro
2010-11-23  9:28 ` Mel Gorman
2010-11-23 23:24   ` Minchan Kim
2010-11-24 10:02     ` Mel Gorman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101123165240.7BC2.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan.kim@gmail.com \
    --cc=npiggin@kernel.dk \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®