From: Julian Anastasov <ja@ssi.bg>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Josue Emmanuel Amaro <Josue.Amaro@oracle.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Value of TASK_UNMAPPED_SIZE on 2.4
Date: Sat, 4 Nov 2000 10:37:54 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.04.10011040953230.511-100000@u> (raw)
In-Reply-To: <20001104015110.A32767@athlon.random>
Hello,
On Sat, 4 Nov 2000, Andrea Arcangeli wrote:
> On Sat, Nov 04, 2000 at 01:09:42AM +0000, Julian Anastasov wrote:
> > Something like the attached old patch for 2.2. It is very
>
> It's not ok for 64bit archs.
Agreed. I see very different definitions for TASK_UNMAPPED_BASE
and ELF_ET_DYN_BASE in all archs and I'm not a guru to make this patch
for all archs but everyone can see the idea. May be the signed int max
value is not suitable for users that need large brk allocations with
more than 2GB on 32bit, i.e. cur_task_unmapped_base is enough. Using
machines with this RAM size and more are already a common practice but
I'm not sure if this feature is so useful compared to the difficulties
to implement it for all archs.
> Andrea
Regards
--
Julian Anastasov <ja@ssi.bg>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-04 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-04 1:09 Julian Anastasov
2000-11-04 0:51 ` Andrea Arcangeli
2000-11-04 10:37 ` Julian Anastasov [this message]
[not found] <fa.d4dt9vv.1gm6abv@ifi.uio.no>
[not found] ` <fa.ebii26v.1mgevrq@ifi.uio.no>
2000-11-03 20:27 ` Kai Harrekilde-Petersen
2000-11-03 20:46 ` Andrea Arcangeli
2000-11-03 22:36 ` Josue Emmanuel Amaro
2000-11-20 2:09 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2000-11-03 19:15 Josue Emmanuel Amaro
2000-11-03 19:37 ` Andrea Arcangeli
2000-11-04 7:39 ` Josue Emmanuel Amaro
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=Pine.LNX.4.04.10011040953230.511-100000@u \
--to=ja@ssi.bg \
--cc=Josue.Amaro@oracle.com \
--cc=andrea@suse.de \
--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
all inboxes | Powered by JetHome®