From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cyrill Gorcunov Subject: Re: [patch 3/7] fs, notify: Add file handle entry into inotify_inode_mark Date: Tue, 13 Nov 2012 18:40:36 +0400 Message-ID: <20121113144036.GI7808@moon> References: <20121112101440.665694060@openvz.org> <20121113082936.GG6511@moon> <2910785.4Vm74eFJyi@deuteros> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: David Rientjes , Andrew Morton , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Al Viro , Alexey Dobriyan , Pavel Emelyanov , James Bottomley , Matthew Helsley , aneesh.kumar@linux.vnet.ibm.com, bfields@fieldses.org To: Tvrtko Ursulin Return-path: Content-Disposition: inline In-Reply-To: <2910785.4Vm74eFJyi@deuteros> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, Nov 13, 2012 at 12:37:23PM +0000, Tvrtko Ursulin wrote: >> Which would give about 26K of additional memory if c/r get used here. >> Not a big number i guess? > > I am pretty sure there are desktop file indexing packages which use > inotify or fanotify which will put a mark on every single directory within > users home. > > You probably need to test this with default installs of popular desktop > environments and realistic home directories. I'm about to shrink the handle down to 40/64 bytes as being proposed in one of early review cycles (i'll do that with patch on top), which should minimize the amount of memory needed (look, it's pretty clear that if the system uses millions of inotify watchers each inotify mark will need the fhandle here in c/r sake, i simply see no way at moment how to escape this completely, but if the c/r is turned off, which is by default, no additional memory needed). p.s.: could you please don't use the html formatted messages