From: "Duraid Madina" <duraid@fl.net.au>
To: "'Randolph Chung'" <randolph@tausq.org>
Cc: <parisc-linux@lists.parisc-linux.org>
Subject: RE: [parisc-linux] Swap space limitions for Linux on parisc
Date: Sat, 9 Mar 2002 14:00:31 +1100 [thread overview]
Message-ID: <000301c1c716$94030b80$022a17ac@simplex> (raw)
In-Reply-To: <20020309024516.GC22385@tausq.org>
> > The 'yet' above gives me hope; will 64 bit user space processes be
> > supported anytime soon? Being able to malloc(1<<36) would be nice!
>
> I sure hope not.... there is a lot of work involved to bring
> up toolchains and all the applications to support two
> different userlands. We still have a lot of work to do just
> to stablize 32-bit userspace. Check the list archives, this
> has been discussed before, and once fairly recently.
I had a bit of a peek around the archives, wow, I guess hppa64 isn't the
most 'comfortable' place for a g++ developer just now.
> This is not to say it couldn't be done of course. This is
> GNU/Linux, you have all the source, go nuts.. :-)
Project deadline soon :( must.. find.. cheap.. 64 bit machine
> But now you have me curious, what app are you writing that
> needs >4G of address space?
A computational physics code. Ideally I would run it in 100s of GB of
RAM. About two months of pain went into making it work (reasonably
efficiently, in theory at least) in 100s of GB of swap.
Now you have *me* curious; I don't mean to be an ignorant asshole, but
what's the point of hppa64 if you *don't* support >4G address space?
*crying* does HP-UX support >4G address space? *finds wallet* :(
Hmm, probably have to shell out more $$$ for the HP compilers too :\
Duraid
next prev parent reply other threads:[~2002-03-09 3:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-09 2:38 [parisc-linux] Swap space limitions for Linux on parisc Duraid Madina
2002-03-09 2:45 ` Randolph Chung
2002-03-09 3:00 ` Duraid Madina [this message]
2002-03-09 3:05 ` Matthew Wilcox
2002-03-09 3:23 ` Duraid Madina
-- strict thread matches above, loose matches on Subject: below --
2002-03-09 5:34 John Marvin
2002-03-09 1:27 John Marvin
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='000301c1c716$94030b80$022a17ac@simplex' \
--to=duraid@fl.net.au \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.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 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.