Date: Mon, 4 Dec 2000 09:47:00 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Matt Dillon <dillon@FreeBSD.ORG> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: cvs commit: src/lib/libc/sys mmap.2 Message-ID: <20001204094700.B546@Odin.AC.HMC.Edu> In-Reply-To: <200012032017.eB3KHaC61682@freefall.freebsd.org>; from dillon@FreeBSD.ORG on Sun, Dec 03, 2000 at 12:17:36PM -0800 References: <200012032017.eB3KHaC61682@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 03, 2000 at 12:17:36PM -0800, Matt Dillon wrote: > dillon 2000/12/03 12:17:36 PST > > Modified files: > lib/libc/sys mmap.2 > Log: > Add warning on file-fragmentation issues related to MAP_NOSYNC I've got a (hopefully) quick question about this warning. If I'm using mmap to create shared memory segments and I don't care about the contents of the file after the run does this fragmentation hurt me? I'm asking because I've got code that uses up to 1.3GB of mmaped storage. The mmaped storage may be larger then physical memory at this point, but the portion I actually use should fit in RAM. Thanks, Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001204094700.B546>