linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: balbir@in.ibm.com
Cc: Paul Jackson <pj@sgi.com>, linux-mm@kvack.org
Subject: Re: [RFC][PATCH] "challenged" memory controller
Date: Thu, 17 Aug 2006 07:47:25 -0700	[thread overview]
Message-ID: <1155826045.9274.44.camel@localhost.localdomain> (raw)
In-Reply-To: <44E447E7.8070502@in.ibm.com>

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

--
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>

  reply	other threads:[~2006-08-17 14:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15 19:20 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 [this message]
2006-08-18  3:33       ` Balbir Singh
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=1155826045.9274.44.camel@localhost.localdomain \
    --to=haveblue@us.ibm.com \
    --cc=balbir@in.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox