[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52612CE6.9080609@hp.com>
Date: Fri, 18 Oct 2013 06:43:18 -0600
From: Thavatchai Makphaibulchoke <thavatchai.makpahibulchoke@...com>
To: Andreas Dilger <adilger@...ger.ca>
CC: Theodore Ts'o <tytso@....edu>, Eric Sandeen <sandeen@...hat.com>,
"linux-ext4@...r.kernel.org List" <linux-ext4@...r.kernel.org>,
"Chandramouleeswaran, Aswin" <aswin@...com>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH v3 0/2] ext4: increase mbcache scalability
On 10/03/2013 09:22 PM, Andreas Dilger wrote:
>
> This is a pretty significant price to pay for SELinux in any case.
> I guess it is probably lower overhead with 256-byte inodes, but
> anything that adds 5-25% overhead shouldn't be taken for granted.
>
> Cheers, Andreas
>
So far we have determined that,
- With SELinux enabled a ramdisk filesytem, with default node size of 128 bytes, extended xattr is generated
- In one of the aim7 workload, mbcache has a hit ratio of about 65%
Seems like mbcache itself and the mbcache lock optimization attempt by the patch could actually improve performance for a real word system where extended xattr is employed. I believe the patch should go in if there isn't any concern.
Please let me know if there is any comment or concern about the patch.
Thanks,
Mak.
--
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
Powered by blists - more mailing lists