search for: full_papers

...feature_hit_mainline_linux https://blogs.oracle.com/wim/entry/from_the_research_department_ramster http://streaming.oracle.com/ebn/podcasts/media/11663326_VM_Linux_042512.mp3 https://oss.oracle.com/projects/tmem/dist/documentation/papers/overcommit.pdf http://static.usenix.org/event/wiov08/tech/full_papers/magenheimer/magenheimer_html/ -- To unsubscribe, send a message with ''unsubscribe linux-mm'' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don''t email: <a href=mailto:"dont@kvack.org"> email@kvack.org <...

...inter, which has no inherent limitations. Note that this is quite expensive and is leaving a potentially huge gap on your stack. > > I'll admit to being curious as to why you actually need larger-than-page-size alignment. Baggy Bounds Checking: http://static.usenix.org/event/sec09/tech/full_papers/sec09_memory.pdf -- John T.

...e tool is to detect uses of uninitialized memory (the major feature of Valgrind/Memcheck not covered by AddressSanitizer). It will also find use-after-destruction-but-before-free in C++. The algorithm of the tool is similar to that of Memcheck ( http://static.usenix.org/event/usenix05/tech/general/full_papers/seward/seward.pdf ). We associate a few shadow bits with every byte of the application memory, poison the shadow of the malloc-ed or alloca-ed memory, load the shadow bits on every memory read, propagate the shadow bits through some of the arithmetic instruction (including MOV), store the shadow bi...

...of uninitialized memory (the > major feature of Valgrind/Memcheck not covered by AddressSanitizer). > It will also find use-after-destruction-but-before-free in C++. > > The algorithm of the tool is similar to that of Memcheck ( > http://static.usenix.org/event/usenix05/tech/general/full_papers/seward/seward.pdf > ). > We associate a few shadow bits with every byte of the application memory, > poison the shadow of the malloc-ed or alloca-ed memory, > load the shadow bits on every memory read, > propagate the shadow bits through some of the arithmetic instruction > (inclu...

On Aug 14, 2012, at 7:31 AM, Baozeng wrote: > Hello all, > I found that the alignment for stack value has no limitation, but for global value, it has a limitation. > > Here is an example: > > #include <stdio.h> > #include <stdlib.h> > > char x[4000] __attribute__((aligned(4096))); > > int > main (int argc, char ** argv) { > char y[4000]

...mory (the >> major feature of Valgrind/Memcheck not covered by AddressSanitizer). >> It will also find use-after-destruction-but-before-free in C++. >> >> The algorithm of the tool is similar to that of Memcheck ( >> http://static.usenix.org/event/usenix05/tech/general/full_papers/seward/seward.pdf >> ). >> We associate a few shadow bits with every byte of the application memory, >> poison the shadow of the malloc-ed or alloca-ed memory, >> load the shadow bits on every memory read, >> propagate the shadow bits through some of the arithmetic ins...

Hello all, I found that the alignment for stack value has no limitation, but for global value, it has a limitation. Here is an example: #include <stdio.h> #include <stdlib.h> char x[4000] __attribute__((aligned(4096))); int main (int argc, char ** argv) { char y[4000] __attribute__((aligned(4096))); printf("x is %p\n", x); printf("y is %p\n", y); return

Hi all, we use SLES 11 and Lustre 1.8.1.1 + patches and like convert a lustre FS using external journals to one with async journals enabled. Question is whether the procedure: umount <filesystem> on all clients umount <osts> on all OSSes e2fsck <ost-device> on all OSSes for all all OSTs tune2fs -O ^has_journal <ost-device> on all

Dear R-help, I've run into a problem loading .RData: I was running a large computation, which supposedly produce a large R object. At the end of the session, I did a save.image() and then quit. The .RData has size 613,249,399 bytes. Now I can't get R to load this .RData file. Whenever I tried, I get "Error: vector memory exhausted (limit reached)". I tried adding

Hi. I've been playing a bit with "use sound card as an entropy source" idea. This simple program does what I wanted: http://people.freebsd.org/~pjd/misc/sndrand.tbz The program is very simple, it should be run with two arguments: % sndtest /dev/dspW 1048576 > rand.data This command will generate 1MB of random data. With my sound card: pcm0: <Intel ICH3 (82801CA)>

I''m a fan of ZFS since I''ve read about it last year. Now I''m on the way to build a home fileserver and I''m thinking to go with Opensolaris and eventually ZFS!! Apart from the other components, the main problem is to choose the motherboard. The offer is incredibly high and I''m lost. Minimum requisites should be: - working well with Open Solaris ;-) -

...expecting the final release by the end of April. Packages for 8.4 have been provided by a fully operational package building cluster. __________________________________________________________________ FreeBSD/arm Superpages for ARMv7 URL: http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf URL: https://wiki.freebsd.org/ARMSuperpages URL: https://github.com/semihalf-bodek-zbigniew/freebsd-arm-superpages.git Contact: Zbigniew Bodek <zbb at semihalf.com> Contact: Grzegorz Bernacki <gjb at semihalf.com> Contact: Rafa? Jaworowski <raj at...

Sep 21 08:57:54 belle fsck: /dev/ad4s1d: 1 DUP I=190 Sep 21 08:57:54 belle fsck: /dev/ad4s1d: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. Ok, so I ran fsck manually (even with -y), but yet it refuses to clear/fix whatever to the questions posed as fsck runs. What does this all mean? Thanks, -Clint -- This message has been scanned for viruses and dangerous content by MailScanner,