Re: [PATCH 0/8] remove i_alloc_sem
From: Jan Kara <jack@suse.cz>
Date: 2011-06-21 23:54:25
Also in:
linux-btrfs, linux-fsdevel
From: Jan Kara <jack@suse.cz>
Date: 2011-06-21 23:54:25
Also in:
linux-btrfs, linux-fsdevel
On Mon 20-06-11 16:15:33, Christoph Hellwig wrote:
i_alloc_sem has always been a bit of an odd "lock". It's the only remaining rw_semaphore that can be released by a different thread than the one that locked it, and it's use case in the core direct I/O code is more like a counter given that the writers already have external serialization. This series removes it in favour of a simpler counter scheme, thus getting rid of the rw_semaphore non-owner APIs as requests by Thomas, while at the same time shrinking the size of struct inode by 160 bytes on 64-bit systems. The only nasty bit is that two filesystems (fat and ext4) have started abusing the lock for their own purposes. I've added a new rw_semaphore
ext4 abuse should be gone when Ted merges my rewrite of ext4_page_mkwrite()... Ted, what happened to that patch. Should I resend it? Honza -- Jan Kara [off-list ref] SUSE Labs, CR