| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20081217005210.GA889@dose.home.local> Date: Wed, 17 Dec 2008 01:52:10 +0100 From: Tino Keitel <tino.keitel@....de> To: linux-kernel@...r.kernel.org Subject: Re: Very slow header cache in mutt if the maildir is on ext3 On Wed, Dec 17, 2008 at 01:16:25 +0100, Tino Keitel wrote: [...] > The strange thing is that in both cases (maildir on ext3 and maildir on > XFS), the header cache file is stored on a separate file system on a > different hard disk on an XFS file system. I don't get the point why > reading the header cache from this XFS file system is so slow when the > maildir is on ext3, and fast when the maildir is on XFS. > > Here are strace excerpts for XFS and ext3, taken with "strace -f -s0 > -tt" after doing "echo 7 > /proc/sys/vm/drop_caches": > > http://tikei.de/mutt_hcache_xfs.txt > http://tikei.de/mutt_hcache_ext3.txt OK, after glancing at the strace output again, I see that the seek offsets are much more linear in the XFS case, whereas they are pretty random in the ext3 case. I guess that this is connected to the order of the files in the maildir, which depends on the FS type. So this is a bug in mutt which makes reading the header cache dead slow if the files are in an inconvenient order. Thanks to Goswin Brederlo for hinting at the seek offsets. Regards, Tino -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists