From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: linux-mm@kvack.org, jschopp@austin.ibm.com,
kamezawa.hiroyu@jp.fujitsu.com, lhms-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/4] Split the free lists into kernel and user parts
Date: Tue, 31 Jan 2006 13:57:19 -0600 [thread overview]
Message-ID: <20060131195718.GA8496@dmt.cnet> (raw)
In-Reply-To: <Pine.LNX.4.58.0601261548190.3279@skynet>
> > Other codepaths which touch page->flags do not hold any lock, so you
> > really must use atomic operations, except when you've guarantee that the
> > page is being freed and won't be reused.
> >
>
> Understood, so I took another look to be sure;
>
> PageEasyRclm() is used on pages that are about to be freed to the main
> or per-cpu allocator so it should be safe.
>
> __SetPageEasyRclm is called when the page is about to be freed. It should
> be safe from concurrent access.
>
> __ClearPageEasyRclm is called when the page is about to be allocated. It
> should be safe.
>
> I think it is guaranteed that there are on concurrent accessing of the
> page flags. Is there something I have missed?
Nope, you are right.
The usage is safe.
--
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-31 19:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 11:54 [PATCH 0/4] Reducing fragmentation using lists (sub-zones) v22 Mel Gorman
2006-01-20 11:54 ` Mel Gorman
2006-01-20 11:54 ` [PATCH 1/4] Add __GFP_EASYRCLM flag and update callers Mel Gorman
2006-01-20 11:54 ` Mel Gorman
2006-01-20 11:54 ` [PATCH 2/4] Split the free lists into kernel and user parts Mel Gorman
2006-01-20 11:54 ` Mel Gorman
2006-01-22 13:31 ` Marcelo Tosatti
2006-01-22 13:31 ` Marcelo Tosatti
2006-01-23 9:39 ` Mel Gorman
2006-01-23 9:39 ` Mel Gorman
2006-01-23 19:13 ` Marcelo Tosatti
2006-01-23 19:13 ` Marcelo Tosatti
2006-01-26 15:55 ` Mel Gorman
2006-01-26 15:55 ` Mel Gorman
2006-01-31 19:57 ` Marcelo Tosatti [this message]
2006-02-05 8:57 ` Coywolf Qi Hunt
2006-02-05 8:57 ` Coywolf Qi Hunt
2006-02-05 9:12 ` Coywolf Qi Hunt
2006-02-05 9:12 ` Coywolf Qi Hunt
2006-01-20 11:55 ` [PATCH 3/4] Split the per-cpu " Mel Gorman
2006-01-20 11:55 ` Mel Gorman
2006-01-20 11:55 ` [PATCH 4/4] Add a configure option for anti-fragmentation Mel Gorman
2006-01-20 11:55 ` 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=20060131195718.GA8496@dmt.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=jschopp@austin.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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.