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: Wed, 04 Jan 2006 00:21:55 +1100 [thread overview]
Message-ID: <43BA7A73.6070407@yahoo.com.au> (raw)
In-Reply-To: <20060103101106.GA3435@dmt.cnet>
Marcelo Tosatti wrote:
> On Tue, Jan 03, 2006 at 04:11:46PM +1100, Nick Piggin wrote:
>
>>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.
>
>
> I see - one point is that the two/three underscore versions make
> it clear that preempt is required, though, but it might be a bit
> over-complicated as you say.
>
> Well, its up to you - please rearrange the patch as you wish and merge
> up?
>
OK I will push it upstream - thanks!
We can revisit details again when some smoke clears from the
coming 2.6.16 merge cycle?
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
WARNING: multiple messages have this Message-ID (diff)
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: Wed, 04 Jan 2006 00:21:55 +1100 [thread overview]
Message-ID: <43BA7A73.6070407@yahoo.com.au> (raw)
In-Reply-To: <20060103101106.GA3435@dmt.cnet>
Marcelo Tosatti wrote:
> On Tue, Jan 03, 2006 at 04:11:46PM +1100, Nick Piggin wrote:
>
>>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.
>
>
> I see - one point is that the two/three underscore versions make
> it clear that preempt is required, though, but it might be a bit
> over-complicated as you say.
>
> Well, its up to you - please rearrange the patch as you wish and merge
> up?
>
OK I will push it upstream - thanks!
We can revisit details again when some smoke clears from the
coming 2.6.16 merge cycle?
--
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 13:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 23:57 [RFC] Event counters [1/3]: Basic counter functionality Christoph Lameter
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 ` Christoph Lameter
2005-12-20 23:57 ` [RFC] Event counters [3/3]: Convert NUMA counters to event counters Christoph Lameter
2005-12-20 23:57 ` Christoph Lameter
2005-12-21 22:24 ` 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 6:46 ` Marcelo Tosatti
2005-12-31 7:54 ` Nick Piggin
2005-12-31 7:54 ` Nick Piggin
2005-12-31 20:26 ` Marcelo Tosatti
2005-12-31 20:26 ` Marcelo Tosatti
2006-01-02 21:40 ` Marcelo Tosatti
2006-01-02 21:40 ` Marcelo Tosatti
2006-01-03 5:11 ` Nick Piggin
2006-01-03 5:11 ` Nick Piggin
2006-01-03 10:11 ` Marcelo Tosatti
2006-01-03 10:11 ` Marcelo Tosatti
2006-01-03 13:21 ` Nick Piggin [this message]
2006-01-03 13:21 ` Nick Piggin
2006-01-03 12:06 ` Marcelo Tosatti
2006-01-03 12:06 ` Marcelo Tosatti
2006-01-03 5:01 ` Nick Piggin
2006-01-03 5:01 ` Nick Piggin
2006-01-03 19:08 ` Christoph Lameter
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=43BA7A73.6070407@yahoo.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.