[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1211130016240.18379@chino.kir.corp.google.com>
Date: Tue, 13 Nov 2012 00:19:25 -0800 (PST)
From: David Rientjes <rientjes@...gle.com>
To: Cyrill Gorcunov <gorcunov@...nvz.org>
cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Al Viro <viro@...iv.linux.org.uk>,
Alexey Dobriyan <adobriyan@...il.com>,
Pavel Emelyanov <xemul@...allels.com>,
James Bottomley <jbottomley@...allels.com>,
Matthew Helsley <matt.helsley@...il.com>,
aneesh.kumar@...ux.vnet.ibm.com, bfields@...ldses.org
Subject: Re: [patch 3/7] fs, notify: Add file handle entry into
inotify_inode_mark
On Tue, 13 Nov 2012, Cyrill Gorcunov wrote:
> > The question is, how many `struct inotify_inode_mark's are instantiated
> > system-wide? Could be millions?
>
> Well, hard to tell, to be fair. On my testing machine only apache has been
> using inotify system as far as I remember, but for sure nothing except memory
> limit the number of inotify. But I think if one running machine with millions
> of inotify it's rather powerful machine with enough memory.
>
Seems easy to determine if you boot with slub_nomerge on the command line
and then read /sys/kernel/slab/inotify_inode_mark/objects. On my system,
that happens to be 210, but I'm sure you could come up with a realistic
synthetic workload to make it much higher.
--
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