From: Andrea Arcangeli <andrea@suse.de>
To: Josue Emmanuel Amaro <Josue.Amaro@oracle.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Value of TASK_UNMAPPED_SIZE on 2.4
Date: Fri, 3 Nov 2000 20:37:43 +0100 [thread overview]
Message-ID: <20001103203743.E15284@athlon.random> (raw)
In-Reply-To: <3A030EE2.92DC3F2@oracle.com>
In-Reply-To: <3A030EE2.92DC3F2@oracle.com>; from Josue.Amaro@oracle.com on Fri, Nov 03, 2000 at 11:15:46AM -0800
On Fri, Nov 03, 2000 at 11:15:46AM -0800, Josue Emmanuel Amaro wrote:
> (page.h). This works out to be a value of 0x4000000.
^ one more zero here
> Are there any negative side effects in defining TASK_UNMAPPED_SIZE to 0x1000000?
I guess you mean 0x10000000. There's no risk in doing that. I also did another
patch that moves the kernel away and allows 3.5G per process on IA32 via plain
mmap or shmat, but it has the downside of reducing a lot the ZONE_NORMAL where
on IA32 buffercache and skb still lives.
Andrea
-
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-03 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 19:15 Value of TASK_UNMAPPED_SIZE on 2.4 Josue Emmanuel Amaro
2000-11-03 19:37 ` Andrea Arcangeli [this message]
2000-11-04 7:39 ` Josue Emmanuel Amaro
[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-04 1:09 Julian Anastasov
2000-11-04 0:51 ` Andrea Arcangeli
2000-11-04 10:37 ` Julian Anastasov
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=20001103203743.E15284@athlon.random \
--to=andrea@suse.de \
--cc=Josue.Amaro@oracle.com \
--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