From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, npiggin@suse.de, hugh@veritas.com,
riel@redhat.com
Subject: Re: [PATCH 2/2] mm: update_page_reclaim_stat() is called form page fault path
Date: Thu, 12 Feb 2009 10:38:44 +0900 (JST) [thread overview]
Message-ID: <20090212103801.C8E1.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <20090211151801.d9e8c84b.akpm@linux-foundation.org>
> > +void update_page_reclaim_stat(struct page *page)
> > +{
> > + struct zone *zone = page_zone(page);
> > +
> > + spin_lock_irq(&zone->lru_lock);
> > + /* if the page isn't reclaimable, it doesn't update reclaim stat */
> > + if (PageLRU(page) && !PageUnevictable(page)) {
> > + update_page_reclaim_stat_locked(zone, page,
> > + !!page_is_file_cache(page), 1);
> > + }
> > + spin_unlock_irq(&zone->lru_lock);
> > +}
>
> And we just added a spin_lock_irq() and a bunch of other stuff to it.
>
> Can we improve this?
>
> Can we just omit it, even?
>
> Can we update those stats locklessly and accomodate the resulting
> inaccuracy over at the codesites where these statistics are actually
> used?
fair enough.
thanks good suggestion.
I'm working it on.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2009-02-12 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 12:33 [PATCH 1/2] mm: don't mark_page_accessed() in do_swap_page() KOSAKI Motohiro
2009-02-11 12:35 ` [PATCH 2/2] mm: update_page_reclaim_stat() is called form page fault path KOSAKI Motohiro
2009-02-11 23:18 ` Andrew Morton
2009-02-12 1:38 ` KOSAKI Motohiro [this message]
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=20090212103801.C8E1.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--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