On Sun, 12.12.10 19:49, John Reiser (jreiser@xxxxxxxxxxxx) wrote: > The project is a database system that creates and dlopen()s > plugins on-the-fly, for better performance on ["long-running"] queries. > We like the speed of creat+write+close+open+read+mmap on /dev/shm. > If /dev/shm and /tmp both become off limits, then what is > the recommended replacement location? The API for /dev/shm is shm_open(). Unless you are using that API you shouldn't really touch /dev/shm. What's wrong with /tmp for your use cases? Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
