(2014/04/02 23:55), One Thousand Gnomes wrote:
Why aren't people just setting the sysctl to a petabyte? What problems
would that lead to?
Historically - hanging on real world desktop systems when someone
accidentally creates a giant SHM segment and maps it.
If you are running with vm overcmmit set to actually do checks then it
*shouldn't* blow up nowdays.
More to the point wtf are people still using prehistoric sys5 IPC APIs
not shmemfs/posix shmem ?
AFAIK, there are many sys5 ipc users.
And admins are using ipcs etc...for checking status. I guess they will not
change the attitude until they see trouble with sysv IPC.
*) I think some RedHat's document(MRG?) says sysv IPC is obsolete clearly but...
I tend to recommend posix shared memory when people newly starts development but
there is an another trap.
IIUC, for posix shmem, an implicit size limit is applied by tmpfs's fs size.
tmpfs mounted on /dev/shm tends to be limited to half size of system memory.
It's hard to know that limit for users before hitting trouble.
Thanks,
-Kame
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>