From: Christoph Lameter <clameter@engr.sgi.com>
To: Robin Holt <holt@sgi.com>
Cc: Mel Gorman <mel@csn.ul.ie>, Russ Anderson <rja@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: How to handle a hugepage with bad physical memory?
Date: Thu, 17 Nov 2005 10:27:35 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.62.0511171026070.20976@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20051117144332.GC4316@lnx-holt.americas.sgi.com>
On Thu, 17 Nov 2005, Robin Holt wrote:
> > > With the new hugepages concept, would it be possible to only mark
> > > the default pagesize portion of a hugepage as bad and then return the
> > > remainder of the hugepage for normal use? What would we basically need
> > > to do to accomplish this? Are there patches in the community which we
> > > should wait to see how they progress before we do any work on this front?
> >
> > On IA64 we have one PTE for a huge page in a different region, so we
> > cannot unmap a page sized section. Other architectures may have PTEs for
> > each page sized section of a huge page. For those it may make sense
> > (but then the management of the page is done via the first page_struct,
> > which likely results in some challenging VM issues).
>
> I think you misunderstood me. I was talking about killing the process.
> All the mappings get destroyed. I want to reclaim as much of that huge
> page as possible.
You are right. If you can reclaim the whole page (as you can when killing
a process) then you can isolate the bad page and free the rest. There
would have to be special code for that in the hugetlb layer.
next prev parent reply other threads:[~2005-11-17 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 13:10 Robin Holt
2005-11-16 19:58 ` Christoph Lameter
2005-11-17 14:43 ` Robin Holt
2005-11-17 14:49 ` Mel Gorman
2005-11-17 18:27 ` Christoph Lameter [this message]
2005-11-16 21:09 ` 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=Pine.LNX.4.62.0511171026070.20976@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=holt@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=rja@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
all inboxes | Powered by JetHome®