> Right, rlimit approach guarantees a simple way of dealing with users > across all tmpfs instances. Which is almost certainly not what you want to happen. Think about direct rendering. For simple stuff tmpfs already supports size/nr_blocks/nr_inodes mount options so you can mount private resource constrained tmpfs objects already without kernel changes. No rlimit hacks needed - and rlimit is the wrong API anyway. Alan -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>