linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Seth, Rohit" <rohit.seth@intel.com>
To: 'William Lee Irwin III' <wli@holomorphy.com>,
	Rohit Seth <rseth@unix-os.sc.intel.com>
Cc: Benjamin LaHaise <bcrl@redhat.com>,
	"Seth, Rohit" <rohit.seth@intel.com>, dada1 <dada1@cosmosbay.com>,
	Christoph Hellwig <hch@infradead.org>,
	Rik van Riel <riel@conectiva.com.br>,
	Andrew Morton <akpm@digeo.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: RE: [patch] remove hugetlb syscalls
Date: Thu, 14 Nov 2002 14:12:06 -0800	[thread overview]
Message-ID: <25282B06EFB8D31198BF00508B66D4FA03EA5AE0@fmsmsx114.fm.intel.com> (raw)


> -----Original Message-----
> From: William Lee Irwin III [mailto:wli@holomorphy.com] 
> > 
> On Thu, Nov 14, 2002 at 12:11:32PM -0800, Rohit Seth wrote:
> > This is not the problem with MAP_SHARED.  It is the lack of  (arch
> > specific) hugepage aligned function support in the kernel. 
> You can use 
> > the mmap on hugetlbfs using only MAP_FIXED with properly aligned 
> > addresses (but then this also is only a hint to kernel).  
> With addr == 
> > NULL in mmap, the function is bound to fail almost all the times.
> 
> There's very little standing in the way of automatic 
> placement. If in your opinion it should be implemented, I'll 
> add that feature today.
> 
mmap with addr==NULL is in my opinion a very useful thing.

> IIRC you mentioned you would like to export the arch-specific 
> hugepage-aligned vma placement functions; once these are 
> available, it should be trivial to reuse them.
> 
> 
I will export those functions from arch specific trees.
--
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/

             reply	other threads:[~2002-11-14 22:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-14 22:12 Seth, Rohit [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-13 23:45 Benjamin LaHaise
2002-11-14  0:42 ` Rik van Riel
2002-11-14  8:52   ` dada1
2002-11-14 14:13     ` Christoph Hellwig
2002-11-14 15:13       ` dada1
2002-11-14 15:31         ` Benjamin LaHaise
2002-11-14 15:38           ` dada1
2002-11-14 20:11           ` Rohit Seth
2002-11-14 20:36             ` William Lee Irwin III
     [not found]           ` <3DD3FED2.2010901@unix-os.sc.intel.com>
2002-11-14 20:01             ` Benjamin LaHaise
2002-11-14 21:06             ` Benjamin LaHaise
2002-11-14 20:30 ` William Lee Irwin III
2002-11-14 20:48   ` Benjamin LaHaise
2002-11-14 21:02     ` William Lee Irwin III
2002-11-14 21:11       ` Benjamin LaHaise
2002-11-14 21:31         ` William Lee Irwin III
2002-11-14 21:40         ` Rohit Seth
2002-11-14 21:59           ` Benjamin LaHaise
2002-11-14 21:06   ` Benjamin LaHaise
2002-11-14 21:06   ` Benjamin LaHaise

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=25282B06EFB8D31198BF00508B66D4FA03EA5AE0@fmsmsx114.fm.intel.com \
    --to=rohit.seth@intel.com \
    --cc=akpm@digeo.com \
    --cc=bcrl@redhat.com \
    --cc=dada1@cosmosbay.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    --cc=rseth@unix-os.sc.intel.com \
    --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