linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: 'David Gibson' <david@gibson.dropbear.id.au>
To: Adam Litke <agl@us.ibm.com>
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 21:01:43 +0100	[thread overview]
Message-ID: <20060413200143.GA13729@localhost.localdomain> (raw)
In-Reply-To: <1144957873.10795.110.camel@localhost.localdomain>

On Thu, Apr 13, 2006 at 02:51:12PM -0500, Adam Litke wrote:
> On Thu, 2006-04-13 at 20:18 +0100, 'David Gibson' wrote:
> > On Thu, Apr 13, 2006 at 12:36:42PM -0500, Adam Litke wrote:
> > > Sorry to bring this up after the strict accounting patch was merged but
> > > things moved along a bit too fast for me to intervene.
> > > 
> > > In the thread beginning at http://lkml.org/lkml/2006/3/8/47 , a
> > > discussion was had to compare the patch from David Gibson (the patch
> > > that was ultimately merged) with an alternative patch from Ken Chen.
> > > The main functional difference is how we handle arbitrary file offsets
> > > into a hugetlb file.  The current patch reserves enough huge pages to
> > > populate the whole file up to the highest file offset in use.  Ken's
> > > patch supported arbitrary blocks.
> > > 
> > > For libhugetlbfs, we would like to have sparsely populated hugetlb files
> > > without wasting all the extra huge pages that the current implementation
> > > requires.  That aside, having yet another difference in behavior for
> > > hugetlbfs files (that isn't necessary) seems like a bad idea.
> > 
> > We would?  Why?
> 
> 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.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

--
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-04-13 20:01 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' [this message]
2006-04-13 20:06       ` Adam Litke
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=20060413200143.GA13729@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=agl@us.ibm.com \
    --cc=akpm@osdl.org \
    --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