The interesting thing is though that when I make the 2 swap partitions regular swap, i.e. not encrypted, then the same program does not get OOM killed and the system stays responsive all the way to the end of allocating the 10GB. So it's not a problem of memory pressure, it's rather related to the fact that the swap is encrypted. nick On Sat, Nov 13, 2010 at 07:53, Arno Wagner <arno@xxxxxxxxxxx> wrote: > On Fri, Nov 12, 2010 at 08:40:43PM -0700, Nicolas Bock wrote: >> I think I have ruled out now that this is a hard crash. I have 8GB of >> physical memory and another 8GB as swap. I allocated 10GB in a C >> program and after it had written to about Â7GB or so, the system >> froze. But after maybe 20 minutes the system got unstuck and had >> killed the job. Since I am on amd64, I am not sure why the job got >> killed, it should certainly have had enough memory to write to. > > I don't know what criteria lead to activation of the OOM killer, > but I use one application that allocates up to 150 MB of memory, > but never uses (accesses) it. This app runs fine in a qemu > with 16MB RAM and 200MB swap. It is possible that your process > gets killed, if it uses more memory than the larger of swap > and main memory. > > Arno > > > -- > Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@xxxxxxxxxxx > GnuPG: ÂID: 1E25338F ÂFP: 0C30 5782 9D93 F785 E79C Â0296 797F 6B50 1E25 338F > ---- > Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans > > If it's in the news, don't worry about it. ÂThe very definition of > "news" is "something that hardly ever happens." -- Bruce Schneier > _______________________________________________ > dm-crypt mailing list > dm-crypt@xxxxxxxx > http://www.saout.de/mailman/listinfo/dm-crypt > _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
