Date: Tue, 29 Jun 2004 02:06:44 +0200 From: Bernd Walter <ticso@cicely12.cicely.de> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/vm vm_map.c Message-ID: <20040629000643.GK1787@cicely12.cicely.de> In-Reply-To: <16608.44441.720450.793280@grasshopper.cs.duke.edu> References: <200406281915.i5SJFeaV060231@repoman.freebsd.org> <20040628224321.GJ1787@cicely12.cicely.de> <16608.44441.720450.793280@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 28, 2004 at 07:45:29PM -0400, Andrew Gallatin wrote:
>
> Bernd Walter writes:
> > On Mon, Jun 28, 2004 at 07:15:40PM +0000, Andrew Gallatin wrote:
> > > gallatin 2004-06-28 19:15:40 UTC
> > >
> > > FreeBSD src repository
> > >
> > > Modified files:
> > > sys/vm vm_map.c
> > > Log:
> > > Fix alpha - the use of min() on longs was loosing the high bits and
> > > returning wrong answers, leading to strange values vm2->vm_{s,t,d}size.
> >
> > Thanks.
> >
> > Would this also explain why setting (MAX|DFL)DSIZ to n*4G never worked?
> >
>
> I don't think so, this was brand-new code.
Ah - OK.
> What's the symptom of MAXDSIZ > 4GB not working? I think the amd64
> people have fixed a lot of bugs in this area on the last few months.
The symptoms were exactly the same as in this case.
It wasn't >4G not working, but n * 4G failed - e.g. 5G was fine.
However - I never tested if the 5G could really be used.
Looked very much like a 31 or 32 bit truncation somewere.
> Have you tried it recently?
No - Never tried those values again - just remembered my last tests a
long time ago.
--
B.Walter BWCT http://www.bwct.de
bernd@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040629000643.GK1787>