From: Balbir Singh <balbir@in.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Paul Jackson <pj@sgi.com>, linux-mm@kvack.org
Subject: Re: [RFC][PATCH] "challenged" memory controller
Date: Fri, 18 Aug 2006 09:03:05 +0530 [thread overview]
Message-ID: <44E534F1.903@in.ibm.com> (raw)
In-Reply-To: <1155826045.9274.44.camel@localhost.localdomain>
Dave Hansen wrote:
> On Thu, 2006-08-17 at 16:11 +0530, Balbir Singh wrote:
>> Would it be possible to protect task->cpuset using rcu_read_lock() for read
>> references as cpuset_update_task_memory_state() does (and use the generations
>> trick to see if a task changed cpusets)? I guess the cost paid is an additional
>> field in the page structure to add generations.
>
> cpusets isn't going to be used long-term here, so we don't really have
> to worry about it.
>
> -- Dave
>
Yes, good point. Thanks for keeping me on course.
--
Balbir Singh,
Linux Technology Center,
IBM Software Labs
--
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-08-18 3:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 19:20 [RFC][PATCH] "challenged" memory controller dave
2006-08-15 22:07 ` Paul Jackson
2006-08-15 22:24 ` Dave Hansen
2006-08-15 22:49 ` Paul Jackson
2006-08-17 10:41 ` Balbir Singh
2006-08-17 14:47 ` Dave Hansen
2006-08-18 3:33 ` Balbir Singh [this message]
2006-08-17 16:34 ` Paul Jackson
2006-08-16 5:44 ` Matt Helsley
2006-08-16 14:00 ` Balbir Singh
2006-08-16 20:31 ` Chandra Seetharaman
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=44E534F1.903@in.ibm.com \
--to=balbir@in.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=pj@sgi.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.