From: Andrea Arcangeli <aarcange@redhat.com>
To: Johannes Weiner <jweiner@redhat.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Michel Lespinasse <walken@google.com>,
Minchan Kim <minchan.kim@gmail.com>,
Hugh Dickins <hughd@google.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>, Mel Gorman <mgorman@suse.de>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Shaohua Li <shaohua.li@intel.com>
Subject: Re: [RFC PATCH 0/3] page count lock for simpler put_page
Date: Sat, 13 Aug 2011 00:22:45 +0200 [thread overview]
Message-ID: <20110812222245.GA12739@redhat.com> (raw)
In-Reply-To: <20110812175206.GB29086@redhat.com>
On Fri, Aug 12, 2011 at 07:52:06PM +0200, Johannes Weiner wrote:
> Do we even need to make this fixed? It can be unsigned long long for
> now, but I could imagine leaving it up to the user depending how much
> space she is able/willing to invest to save time:
>
> void synchronize_rcu_with(unsigned long time, unsigned int bits)
> {
> if (generation_counter & ((1 << bits) - 1) == time)
> synchronize_rcu();
> }
>
> If you have only 3 bits to store the time, you will synchronize
> falsely to every 8th phase. Better than nothing, right?
Ok if any of the bits is different we can safely skip it.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-12 22:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 21:07 [RFC PATCH 0/3] page count lock for simpler put_page Michel Lespinasse
2011-08-04 21:07 ` [RFC PATCH 1/3] mm: Replace naked page->_count accesses with accessor functions Michel Lespinasse
2011-08-04 21:07 ` [RFC PATCH 2/3] mm: page count lock Michel Lespinasse
2011-08-07 14:00 ` Minchan Kim
2011-08-04 21:07 ` [RFC PATCH 3/3] mm: get_first_page_unless_zero() Michel Lespinasse
2011-08-07 14:13 ` Minchan Kim
2011-08-05 6:39 ` [RFC PATCH 0/3] page count lock for simpler put_page Michel Lespinasse
2011-08-07 14:25 ` Minchan Kim
2011-08-09 11:04 ` Michel Lespinasse
2011-08-09 22:22 ` Minchan Kim
2011-08-12 22:35 ` Michel Lespinasse
2011-08-13 4:07 ` Minchan Kim
2011-08-12 15:36 ` Andrea Arcangeli
2011-08-12 16:08 ` SPAM: " Paul E. McKenney
2011-08-12 16:43 ` Andrea Arcangeli
2011-08-12 17:27 ` Paul E. McKenney
2011-08-12 23:45 ` Michel Lespinasse
2011-08-13 1:57 ` Paul E. McKenney
2011-08-13 23:56 ` Andrea Arcangeli
2011-08-13 4:18 ` Minchan Kim
2011-08-12 16:57 ` Johannes Weiner
2011-08-12 17:08 ` Andrea Arcangeli
2011-08-12 17:52 ` Johannes Weiner
2011-08-12 18:13 ` Paul E. McKenney
2011-08-12 19:05 ` Johannes Weiner
2011-08-12 22:14 ` Paul E. McKenney
2011-08-12 22:22 ` Andrea Arcangeli [this message]
2011-08-12 18:03 ` Paul E. McKenney
2011-08-12 17:41 ` Paul E. McKenney
2011-08-12 17:56 ` Johannes Weiner
2011-08-12 23:02 ` Michel Lespinasse
2011-08-12 22:50 ` Michel Lespinasse
2011-08-13 4:11 ` Minchan Kim
2011-08-12 16:58 ` Andrea Arcangeli
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=20110812222245.GA12739@redhat.com \
--to=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=jweiner@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan.kim@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=riel@redhat.com \
--cc=shaohua.li@intel.com \
--cc=walken@google.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;
as well as URLs for NNTP newsgroup(s).