Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932131Ab2HUNAX (ORCPT ); Tue, 21 Aug 2012 09:00:23 -0400 Received: from mailhub.sw.ru ([195.214.232.25]:36639 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932101Ab2HUNAS (ORCPT ); Tue, 21 Aug 2012 09:00:18 -0400 Message-ID: <5033864A.5040809@parallels.com> Date: Tue, 21 Aug 2012 16:59:54 +0400 From: Pavel Emelyanov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120209 Thunderbird/10.0.1 MIME-Version: 1.0 To: Boaz Harrosh CC: "J. Bruce Fields" , "Aneesh Kumar K.V" , Al Viro , Cyrill Gorcunov , "linux-kernel@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , Alexey Dobriyan , Andrew Morton , James Bottomley , Matthew Helsley Subject: Re: [patch 4/8] fs, exportfs: Add export_encode_inode_fh helper References: <20120820183225.GB4911@fieldses.org> <20120820190606.GE27443@moon> <20120820193204.GD5779@fieldses.org> <50335261.5090504@parallels.com> <87wr0sle4v.fsf@skywalker.in.ibm.com> <503367CB.9080609@parallels.com> <20120821105424.GA7670@moon> <50336C51.60501@parallels.com> <20120821121155.GC9483@fieldses.org> <50337D87.90607@parallels.com> <20120821122908.GE9483@fieldses.org> <50338458.7090602@panasas.com> In-Reply-To: <50338458.7090602@panasas.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1154 Lines: 35 On 08/21/2012 04:51 PM, Boaz Harrosh wrote: > On 08/21/2012 03:29 PM, J. Bruce Fields wrote: > <> > >> OK. So if you don't mind the fact that there are filesystems with >> inotify support but not filehandle support, then I think generating a >> filehandle early as you describe would work. I guess it's a little more >> memory per watched inode. >> > > > For the minority of FSs that do not have a filehandle support it should > be easy to generate a generic one, that should work 95% of the time. Yup, this is how exportfd_encode_fh currently works. > Are we guaranteed that after the checkpoint restore the version of > the Kernel is the same as the one that did the checkpoint? If yes > then I don't see any problem. Strictly speaking -- no we don't. Migration should to work across kernel versions (from older to newer). Why kernel version matters in this case? >> --b. > > > Cheers > Boaz > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/