From: Adam Litke <agl@us.ibm.com>
To: 'David Gibson' <david@gibson.dropbear.id.au>
Cc: akpm@osdl.org, "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
wli@holomorphy.com, linux-mm@kvack.org
Subject: Re: [RFD hugetlbfs] strict accounting and wasteful reservations
Date: Thu, 13 Apr 2006 15:06:44 -0500 [thread overview]
Message-ID: <1144958804.10795.111.camel@localhost.localdomain> (raw)
In-Reply-To: <20060413200143.GA13729@localhost.localdomain>
On Thu, 2006-04-13 at 21:01 +0100, 'David Gibson' wrote:
> > We are thinking about switching the implementation of the ELF segment
> > remapping code to store all of the remapped segments in one hugetlbfs
> > file. That way we have one hugetlb file per executable. This makes
> > managing the segments much easier, especially when doing things like
> > global sharing. When doing this, we'd like the file offset to
> > correspond to the virtual address of the mapped segment. So I admit
> > that altering the kernel behavior helps libhugetlbfs, but I think my
> > second justification above is even more important. I like removing
> > anomalies from hugetlbfs whenever possible.
>
> Hrm... I'm not entirely convinced attempting to directly map vaddr to
> file offset is a good idea. But give it a shot, I guess.
It works, but just wastes a ton of huge pages in the process.
--
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center
--
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-04-13 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 17:36 Adam Litke
2006-04-13 19:18 ` 'David Gibson'
2006-04-13 19:51 ` Adam Litke
2006-04-13 20:01 ` 'David Gibson'
2006-04-13 20:06 ` Adam Litke [this message]
2006-04-13 21:32 ` 'David Gibson'
2006-04-14 1:55 ` Chen, Kenneth W
2006-04-14 17:33 ` Adam Litke
2006-04-14 17:40 ` Chen, Kenneth W
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=1144958804.10795.111.camel@localhost.localdomain \
--to=agl@us.ibm.com \
--cc=akpm@osdl.org \
--cc=david@gibson.dropbear.id.au \
--cc=kenneth.w.chen@intel.com \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.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