From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: 'Adam Litke' <agl@us.ibm.com>
Cc: 'David Gibson' <david@gibson.dropbear.id.au>,
akpm@osdl.org, wli@holomorphy.com, linux-mm@kvack.org
Subject: RE: [RFD hugetlbfs] strict accounting and wasteful reservations
Date: Fri, 14 Apr 2006 10:40:13 -0700 [thread overview]
Message-ID: <4t16i2$m7o67@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1145036008.10795.122.camel@localhost.localdomain>
Adam Litke wrote on Friday, April 14, 2006 10:33 AM
> On Thu, 2006-04-13 at 18:55 -0700, Chen, Kenneth W wrote:
> > Arbitrary offset isn't that bad, here is the patch that I forward port to
> > 2.6.17-rc1. It is just 35 lines more. Another thing I can do is to put
> > the variable region tracking code into a library function, maybe that will
> > help to move it along? I'm with Adam, I don't like to see hugetlbfs have
> > yet another uncommon behavior.
>
> Thanks Ken. The patch passes the libhugetlbfs test suite and also works
> as advertised for sparse mappings. I don't recall, is this the version
> you and David were converging on before Dave's patch was merged? I seem
> to remember a few iterations of this patch centered locking discussions,
> etc.
Adam, yes, this is the latest rev includes all the comments from David.
- Ken
--
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>
prev parent reply other threads:[~2006-04-14 17:40 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
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 [this message]
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='4t16i2$m7o67@orsmga001.jf.intel.com' \
--to=kenneth.w.chen@intel.com \
--cc=agl@us.ibm.com \
--cc=akpm@osdl.org \
--cc=david@gibson.dropbear.id.au \
--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