Re: VM: file swapping (this time in libc): patch

2002-03-13 Thread Matthew Dillon
Oops. I'm sorry! This was an email all the from last october! I didn't mean to resurrect the thread :-) -Matt :ehlo. : : I was told that diff format I used is unappropriate for most cases, : so I redo it in unified (-u) format. : : Purpose: t

Re: VM: file swapping (this time in libc): patch

2002-03-13 Thread Matthew Dillon
Ok, there are two rather serious problems with this patch: (1) When you use a MAP_PRIVATE mapping, modifications to the mapped memory are backed by swap, not by the file. That is what MAP_PRIVATE does by definition. (2) You can't safely use MAP_SHARED unless you also

Re: VM: file swapping (this time in libc): patch

2001-10-04 Thread Vladimir Dozen
ehlo. I was told that diff format I used is unappropriate for most cases, so I redo it in unified (-u) format. Purpose: to allow developers of large applications to use system memory allocation routines for allocating in mmap()ed file instead of writing own ones. Also, allow to run app

Re: VM: file swapping (this time in libc): patch

2001-10-03 Thread Vladimir Dozen
ehlo. > I once had a patch to phkmalloc() which backed all malloc'ed VM with > hidden files in the users homedir. It was written to put the VM > usage under QUOTA control, but it had many useful side effects as well. > > I can't seem to find it right now, but it is trivial to do: just > replace