All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Bryant <raybry@sgi.com>
To: 'David Gibson' <david@gibson.dropbear.id.au>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	lse-tech@lists.sourceforge.net,
	'Andy Whitcroft' <apw@shadowen.org>,
	'Andrew Morton' <akpm@osdl.org>
Subject: Re: hugetlb demand paging patch part [2/3]
Date: Fri, 16 Apr 2004 19:05:13 +0000	[thread overview]
Message-ID: <40802E69.7040506@sgi.com> (raw)
In-Reply-To: <20040416044917.GB26707@zax>

David,

Is there a big user demand for copy-on-write support for hugetlb pages?
I can understand the rationale for making hugetlb pages behave more like user 
pages, and fixing the problem that hugetlb pages are shared across fork via 
MAP_SHARE semantics regardless of whether the user requests MAP_PRIVATE or 
not, but it just doesn't strike me as something that anyone who uses hugetlb 
pages would actually want.

Of course, YRMV (your requirements may vary).  :-)

'David Gibson' wrote:
> 
> Well, I'm attempting to understand the hugepage code across all the
> archs, so that I can try to implement copy-on-write with a minimum of
> arch specific gunk.  Simplifying and consolidating the existing code
> across archs would be a helpful first step, if possible.
> 

-- 
Best Regards,
Ray
-----------------------------------------------
                   Ray Bryant
512-453-9679 (work)         512-507-7807 (cell)
raybry@sgi.com             raybry@austin.rr.com
The box said: "Requires Windows 98 or better",
            so I installed Linux.
-----------------------------------------------


WARNING: multiple messages have this Message-ID (diff)
From: Ray Bryant <raybry@sgi.com>
To: "'David Gibson'" <david@gibson.dropbear.id.au>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	lse-tech@lists.sourceforge.net,
	"'Andy Whitcroft'" <apw@shadowen.org>,
	"'Andrew Morton'" <akpm@osdl.org>
Subject: Re: hugetlb demand paging patch part [2/3]
Date: Fri, 16 Apr 2004 14:05:13 -0500	[thread overview]
Message-ID: <40802E69.7040506@sgi.com> (raw)
In-Reply-To: <20040416044917.GB26707@zax>

David,

Is there a big user demand for copy-on-write support for hugetlb pages?
I can understand the rationale for making hugetlb pages behave more like user 
pages, and fixing the problem that hugetlb pages are shared across fork via 
MAP_SHARE semantics regardless of whether the user requests MAP_PRIVATE or 
not, but it just doesn't strike me as something that anyone who uses hugetlb 
pages would actually want.

Of course, YRMV (your requirements may vary).  :-)

'David Gibson' wrote:
> 
> Well, I'm attempting to understand the hugepage code across all the
> archs, so that I can try to implement copy-on-write with a minimum of
> arch specific gunk.  Simplifying and consolidating the existing code
> across archs would be a helpful first step, if possible.
> 

-- 
Best Regards,
Ray
-----------------------------------------------
                   Ray Bryant
512-453-9679 (work)         512-507-7807 (cell)
raybry@sgi.com             raybry@austin.rr.com
The box said: "Requires Windows 98 or better",
            so I installed Linux.
-----------------------------------------------


  reply	other threads:[~2004-04-16 19:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13 23:22 hugetlb demand paging patch part [2/3] Chen, Kenneth W
2004-04-13 23:22 ` Chen, Kenneth W
2004-04-15  7:17 ` David Gibson
2004-04-15  7:17   ` David Gibson
2004-04-15 17:27 ` Chen, Kenneth W
2004-04-15 17:27   ` Chen, Kenneth W
2004-04-16  2:34   ` 'David Gibson'
2004-04-16  2:34     ` 'David Gibson'
2004-04-16  2:58 ` Chen, Kenneth W
2004-04-16  2:58   ` Chen, Kenneth W
2004-04-16  3:27   ` 'David Gibson'
2004-04-16  3:27     ` 'David Gibson'
2004-04-16  4:13 ` Chen, Kenneth W
2004-04-16  4:13   ` Chen, Kenneth W
2004-04-16  4:49   ` 'David Gibson'
2004-04-16  4:49     ` 'David Gibson'
2004-04-16 19:05     ` Ray Bryant [this message]
2004-04-16 19:05       ` Ray Bryant
2004-04-17 12:05       ` 'David Gibson'
2004-04-17 12:05         ` 'David Gibson'
2004-04-18 17:36         ` [Lse-tech] " Ray Bryant
2004-04-18 17:36           ` Ray Bryant
2004-04-19  0:47           ` 'David Gibson'
2004-04-19  0:47             ` 'David Gibson'
2004-04-16  5:56 ` Chen, Kenneth W
2004-04-16  5:56   ` Chen, Kenneth W
2004-04-16  6:15   ` 'David Gibson'
2004-04-16  6:15     ` 'David Gibson'

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=40802E69.7040506@sgi.com \
    --to=raybry@sgi.com \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=kenneth.w.chen@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.