From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Christoph Lameter <clameter@sgi.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Andi Kleen <ak@suse.de>
Subject: Re: [RFC] Event counters [1/3]: Basic counter functionality
Date: Tue, 03 Jan 2006 16:11:46 +1100 [thread overview]
Message-ID: <1136265106.5261.34.camel@npiggin-nld.site> (raw)
In-Reply-To: <20060102214016.GA13905@dmt.cnet>
On Mon, 2006-01-02 at 19:40 -0200, Marcelo Tosatti wrote:
> Nick,
>
> The following patch:
>
> - Moves the lightweight "inc/dec" versions of mod_page_state variants
> to three underscores, making those the default for locations where enough
> locks are held.
>
I guess I was hoping to try to keep it simple, and just have two
variants, the __ version would require the caller to do the locking.
In cases like eg. allocstall, they should happen infrequently enough
that the extra complexity is probably not worth worrying about.
I don't think I commented about the preempt race though (and requirement
to have preempt off from process context), which obviously can be a
problem as you say (though I think things are currently safe?).
> - Make the two-underscore version disable and enable preemption, which
> is required to avoid preempt-related races which can result in missed
> updates.
>
> - Extends the lightweight version usage in page reclaim,
> pte allocation, and a few other codepaths.
>
I guess nr_dirty looks OK in the places it can be put under tree_lock.
nr_page_table_pages is OK because ptl should be held to prevent preempt.
pgrotated and pgactivate should be good because of lru_lock.
Thanks for going through these!
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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>
next prev parent reply other threads:[~2006-01-03 5:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 23:57 Christoph Lameter
2005-12-20 23:57 ` [RFC] Event counters [2/3]: Convert inc_page_state -> count_event Christoph Lameter
2005-12-20 23:57 ` [RFC] Event counters [3/3]: Convert NUMA counters to event counters Christoph Lameter
2005-12-21 22:24 ` Christoph Lameter
2005-12-31 6:46 ` [RFC] Event counters [1/3]: Basic counter functionality Marcelo Tosatti
2005-12-31 7:54 ` Nick Piggin
2005-12-31 20:26 ` Marcelo Tosatti
2006-01-02 21:40 ` Marcelo Tosatti
2006-01-03 5:11 ` Nick Piggin [this message]
2006-01-03 10:11 ` Marcelo Tosatti
2006-01-03 13:21 ` Nick Piggin
2006-01-03 12:06 ` Marcelo Tosatti
2006-01-03 5:01 ` Nick Piggin
2006-01-03 19:08 ` Christoph Lameter
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=1136265106.5261.34.camel@npiggin-nld.site \
--to=nickpiggin@yahoo.com.au \
--cc=ak@suse.de \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.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