From: Kai Harrekilde-Petersen <Kai.Harrekilde-Petersen@exbit.dk>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Value of TASK_UNMAPPED_SIZE on 2.4
Date: 03 Nov 2000 21:27:07 +0100 [thread overview]
Message-ID: <80snp8reck.fsf@orthanc.exbit-technology.com> (raw)
In-Reply-To: <fa.d4dt9vv.1gm6abv@ifi.uio.no> <fa.ebii26v.1mgevrq@ifi.uio.no>
In-Reply-To: Andrea Arcangeli's message of "Fri, 3 Nov 2000 19:38:34 GMT"
Andrea Arcangeli <andrea@suse.de> writes:
> 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.
Is this available as a patch, or preferably as a compilation option to
the standard kernel?
The ASIC tools that we use wants all the memory they can grab, and the
extra few hundred megs can sometimes be _very_ critical. On Solaris,
Synopsys' Design Compiler can allocate 3.8Gig and we've hit that limit
hard when working with toplevel netlists and SDF databases.
Thanks in advance,
Kai
--
Kai Harrekilde-Petersen
-
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 parent reply other threads:[~2000-11-03 20:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.d4dt9vv.1gm6abv@ifi.uio.no>
[not found] ` <fa.ebii26v.1mgevrq@ifi.uio.no>
2000-11-03 20:27 ` Kai Harrekilde-Petersen [this message]
2000-11-03 20:46 ` Value of TASK_UNMAPPED_SIZE on 2.4 Andrea Arcangeli
2000-11-03 22:36 ` Josue Emmanuel Amaro
2000-11-20 2:09 ` Andrea Arcangeli
2000-11-04 1:09 Julian Anastasov
2000-11-04 0:51 ` Andrea Arcangeli
2000-11-04 10:37 ` Julian Anastasov
-- 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=80snp8reck.fsf@orthanc.exbit-technology.com \
--to=kai.harrekilde-petersen@exbit.dk \
--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 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.