FW: C000629-3365

From: jrjame - John James <jrjame_at_acxiom.com>
Date: Wed, 05 Jul 2000 08:00:13 -0500

Below is the response I received from Compaq regarding the 1 GB memory
mapping limit that is mentioned in the release notes for 4.0G. This was of
great concern to me because we have 2 GS-320's on the way with 32 GB of RAM
each and we are going to be doing 64 + GB of mmap. I would like to say
thanks to Claude Scarpelli for noticing this and bringing to our attention.

John R. James Jr.
Unix Systems Engineer
Applied Infrastructure Technology
Acxiom, Corp.
501-342-3061
jrjame_at_acxiom.com


-----Original Message-----
From: Rubens, Jay [mailto:Jay.Rubens_at_COMPAQ.com]
Sent: Monday, July 03, 2000 4:05 PM
To: 'jrjame_at_acxiom.com'
Subject: Re: C000629-3365


John,

I have engineering feed back regarding your memory map issue.
It looks like a matter of semantics, more than one way to
interpret the documentation.

Basically, the reference means is that if a file is more that
1GB, it will require more that 1 segment to hold it, not that
there is a file limit of 1GB. Large files will utilize multiple
segments.

>From the engineer, Keith Martin:
I am the UNIX Support Engineering Group (USEG) engineer to whom this
case has been assigned:

Memory Mapped File Limit
The supported maximum size of a file that can be mapped into
memory without segmenting the file is 1Gb.

"This just tells me a file larger than 1 Gb will be mmap-ed
into several different memory segments --- not this is
the absolute largest size for an mmap-ed file."

So, bring on the big files.

Best regards,

Jay Rubens
Compaq Services
Technical Account Manager
Business Critical Gold/UNIX
Phone: 281.927.1931
Jay.Rubens_at_Compaq.com
 
Received on Wed Jul 05 2000 - 12:58:35 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:40 NZDT