search for: aio_mnt

...turn mount_pseudo(fs_type, "aio:", NULL, &ops, AIO_RING_MAGIC); } and static struct file_system_type aio_fs = { .name = "aio", .mount = aio_mount, .kill_sb = kill_anon_super, }; aio_mnt = kern_mount(&aio_fs); All of 12 lines. Your export is not much shorter. To quote old mail on the same topic: > Note that anon_inodes.c reason to exist was "it's for situations where > all context lives on struct file and we don't need separate inode for > them"....

...turn mount_pseudo(fs_type, "aio:", NULL, &ops, AIO_RING_MAGIC); } and static struct file_system_type aio_fs = { .name = "aio", .mount = aio_mount, .kill_sb = kill_anon_super, }; aio_mnt = kern_mount(&aio_fs); All of 12 lines. Your export is not much shorter. To quote old mail on the same topic: > Note that anon_inodes.c reason to exist was "it's for situations where > all context lives on struct file and we don't need separate inode for > them"....

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.