search for: names_cach

...ut nobody there seems to be interested in what i found out. since i believe this is a serious bug, i'm posting my perception again... the bug is about the handling of bad inodes in at least the 2.4.16, .17, .18-pre9 and .9 kernel releases (i suspect all 2.4 kernels are affected) and causes the names_cache to get confused. however, it is actually not a bug in ext[23] but in vfs layer. you can easily reproduce this effect by making an inode bad using debugfs (or using a bad one if you have, of course) and open() it with the flag O_CREAT set. watching /proc/slabinfo will show you the weirdness. cons...

...bdev_cache 56 56 512 7 1 sysfs_dir_cache 4831 4876 40 92 1 mnt_cache 30 60 128 30 1 inode_cache 1041 1276 356 11 1 dentry_cache 11588 13688 132 29 1 filp 2734 2820 192 20 1 names_cache 25 25 4096 1 1 idr_layer_cache 204 232 136 29 1 buffer_head 456669 459936 52 72 1 mm_struct 109 126 448 9 1 vm_area_struct 5010 5632 88 44 1 fs_cache 109 177 64 59 1 files_cach...

...1020 320 12 1 : tunables 54 27 8 : slabdata 85 85 0 dentry_cache 42325 42336 140 28 1 : tunables 120 60 8 : slabdata 1512 1512 0 filp 517 645 256 15 1 : tunables 120 60 8 : slabdata 43 43 0 names_cache 4 4 4096 1 1 : tunables 24 12 8 : slabdata 4 4 0 idr_layer_cache 110 145 136 29 1 : tunables 120 60 8 : slabdata 5 5 0 buffer_head 18944 18954 48 81 1 : tunables 120 60 8 : slabdata 234...

...82 90 448 9 sysfs_dir_cache 13325 13340 40 92 mnt_cache 21 30 128 30 inode_cache 2416 2976 312 12 dentry_cache 4407 12989 124 31 filp 710 1060 192 20 names_cache 2 2 4096 1 idr_layer_cache 209 232 136 29 Cache Num Total Size Pages buffer_head 25038 28938 48 78 mm_struct 87 90 448 9 vm_area_struct 1782 2478 92...

Hi Guys, My users are reporting some issues with memory on our lustre 1.8.1 clients. It looks like when they submit a single job at a time the run time was about 4.5 minutes. However, when they ran multiple jobs (10 or less) on a client with 192GB of memory on a single node the run time for each job was exceeding 3-4X the run time for the single process. They also noticed that the swap space

Next version of https://patchwork.freedesktop.org/series/48596/ . Made some important changes to the refactoring patch, but everything else is the same. Lyude Paul (5): drm/nouveau: Check backlight IDs are >= 0, not > 0 drm/nouveau: Move backlight device into nouveau_connector drm/nouveau: s/nouveau_backlight_exit/nouveau_backlight_fini/ drm/nouveau: Cleanup indenting in

This series fixes some issues with nouveau's backlight support that were causing kernel panics on module reloads, specifically on systems with nouveau handling the backlight of one of the displays. While we're at it, let's cleanup nouveau_backlight.c as well Lyude Paul (5): drm/nouveau: Check backlight IDs are >= 0, not > 0 drm/nouveau: Move backlight device into

Next version of https://patchwork.freedesktop.org/series/48596/ . Added NV_INFO_ONCE and made "Move backlight device into nouveau_connector" use that instead so we don't print the GMUX warning more then once. Lyude Paul (5): drm/nouveau: Add NV_PRINTK_ONCE and variants drm/nouveau: Move backlight device into nouveau_connector drm/nouveau:

Forgot to send 6 patches instead of five since there's one new one now, whoops! No actual changes, next version of https://patchwork.freedesktop.org/series/48596/ Lyude Paul (6): drm/nouveau: Check backlight IDs are >= 0, not > 0 drm/nouveau: Add NV_PRINTK_ONCE and variants drm/nouveau: Move backlight device into nouveau_connector drm/nouveau:

Refactor for Ben, hopefully this time this should apply to his tree. Next version of https://patchwork.freedesktop.org/series/48596/ No changes otherwise. Lyude Paul (6): drm/nouveau: Check backlight IDs are >= 0, not > 0 drm/nouveau: Add NV_PRINTK_ONCE and variants drm/nouveau: Move backlight device into nouveau_connector drm/nouveau: