linux-ext4 - Re: [PATCH 3/3] ext4: optimize quota write locking

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100401091414.GF3322@quack.suse.cz>
Date:	Thu, 1 Apr 2010 11:14:14 +0200
From:	Jan Kara <jack@...e.cz>
To:	Dmitry Monakhov <dmonakhov@...nvz.org>
Cc:	linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	jack@...e.cz
Subject: Re: [PATCH 3/3] ext4: optimize quota write locking

On Sat 27-03-10 15:15:40, Dmitry Monakhov wrote:
> Quota inode is append only. In most cases writes performed
> to allocated blocks before i_size. Currently we grup i_mutex
> for each quota write to protect i_size and i_mtime. But in most
> cases i_size not changed. And i_mtime is not that important
> as for regular files. So let's update it only when quota file
> increased. This allow us to avoid i_mutex in most cases.
  But this won't help performance at all because dqio_mutex serializes
writes to the file already, right?

								Honza

-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html