From: Andrea Arcangeli <andrea@suse.de>
To: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.22pre6aa1
Date: Sat, 19 Jul 2003 00:27:50 +0200 [thread overview]
Message-ID: <20030718222750.GL3928@dualathlon.random> (raw)
In-Reply-To: <20030718191853.A11052@infradead.org>
On Fri, Jul 18, 2003 at 07:18:53PM +0100, Christoph Hellwig wrote:
> On Thu, Jul 17, 2003 at 12:28:57PM +0200, Andrea Arcangeli wrote:
> > Only in 2.4.21rc8aa1: 9910_shm-largepage-13.gz
> > Only in 2.4.22pre6aa1: 9910_shm-largepage-16.gz
> >
> > Thanks to Hugh for the help in porting the bigpages
> > to the rewritten shmfs layer in 22pre. No idea at the moment if it
> > works or if it only compiles.
>
> Any reason you don't use a backport of hugetlbfs like the IA64 or
> the RH AS3 tree?
bigpages= is a documented API that has to be used in production, so I
can easily add the hugetlbfs API but I guess I've to keep this one
anyways. I also would need to verify the performance of hugetlbfs before
suggesting migrating to it, for example I don't want
preallocation/prefaulting (IIRC hugetlbfs preallocates everything). I
also like the single huge array of page pointers, that is very hardwired
but optimal for those workloads.
Andrea
next prev parent reply other threads:[~2003-07-18 22:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 10:28 2.4.22pre6aa1 Andrea Arcangeli
2003-07-17 10:42 ` 2.4.22pre6aa1 ooyama eiichi
2003-07-17 10:52 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 10:53 ` 2.4.22pre6aa1 ooyama eiichi
2003-07-17 15:42 ` 2.4.22pre6aa1 Dave Jones
2003-07-17 20:31 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-17 22:13 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 22:26 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-17 22:27 ` 2.4.22pre6aa1 Mike Fedyk
2003-07-17 22:32 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 22:30 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 22:50 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 0:30 ` 2.4.22pre6aa1 Chris Mason
2003-07-22 12:28 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-22 14:04 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 5:47 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-22 13:34 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-22 13:59 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-24 12:27 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-24 14:14 ` 2.4.22pre6aa1 Chris Mason
2003-07-18 18:18 ` 2.4.22pre6aa1 Christoph Hellwig
2003-07-18 22:27 ` Andrea Arcangeli [this message]
2003-07-18 22:48 ` 2.4.22pre6aa1 William Lee Irwin III
2003-07-18 22:53 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 23:04 ` 2.4.22pre6aa1 William Lee Irwin III
2003-07-18 23:12 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 23:53 ` 2.4.22pre6aa1 William Lee Irwin III
2003-07-19 0:04 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-23 11:21 2.4.22pre6aa1 Sergey S. Kostyliov
2003-07-25 5:28 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-25 11:10 ` 2.4.22pre6aa1 Sergey S. Kostyliov
2003-07-25 19:02 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-08-03 17:12 ` 2.4.22pre6aa1 Sergey S. Kostyliov
2003-08-16 11:56 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-08-16 13:54 ` 2.4.22pre6aa1 Hugh Dickins
2003-08-16 14:00 ` 2.4.22pre6aa1 Hugh Dickins
2003-08-16 14:50 ` 2.4.22pre6aa1 Sergey S. Kostyliov
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=20030718222750.GL3928@dualathlon.random \
--to=andrea@suse.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).