From mboxrd@z Thu Jan  1 00:00:00 1970
From: Liu Bo <bo.li.liu@oracle.com>
Date: Fri, 3 Feb 2017 10:31:56 -0800
Subject: [Cluster-devel] [PATCH 04/24] fs: Provide infrastructure for
 dynamic BDIs in filesystems
In-Reply-To: <20170203135042.GB5844@quack2.suse.cz>
References: <20170202173422.3240-1-jack@suse.cz>
	<20170202173422.3240-5-jack@suse.cz>
	<20170202192827.GF6550@localhost.localdomain>
	<20170203135042.GB5844@quack2.suse.cz>
Message-ID: <20170203183155.GA30842@localhost.localdomain>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

On Fri, Feb 03, 2017 at 02:50:42PM +0100, Jan Kara wrote:
> On Thu 02-02-17 11:28:27, Liu Bo wrote:
> > Hi,
> > 
> > On Thu, Feb 02, 2017 at 06:34:02PM +0100, Jan Kara wrote:
> > > Provide helper functions for setting up dynamically allocated
> > > backing_dev_info structures for filesystems and cleaning them up on
> > > superblock destruction.
> > 
> > Just one concern, will this cause problems for multiple superblock cases
> > like nfs with nosharecache?
> 
> Can you ellaborate a bit? I've looked for a while what nfs with
> nosharecache does but I didn't see how it would influence anything with
> bdis...

Oh, I missed that bdi_seq was static, then it should be fine.

(I was worried about that nfs with nosharecache would have multiple
superblocks and if each superblock has a bdi using the same bdi name,
nfs-xx.)

Thanks for the reply.

Thanks,

-liubo