linux-nilfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Jan Kara <jack@suse.cz>
Cc: codalist@TELEMANN.coda.cs.cmu.edu, linux-block@vger.kernel.org,
	linux-nfs@vger.kernel.org, linux-nilfs@vger.kernel.org,
	linux-cifs@vger.kernel.org, ecryptfs@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	cluster-devel@redhat.com, linux-mtd@lists.infradead.org,
	osd-dev@open-osd.org, linux-fsdevel@vger.kernel.org,
	v9fs-developer@lists.sourceforge.net, ceph-devel@vger.kernel.org,
	Petr Vandrovec <petr@vandrovec.name>,
	linux-afs@lists.infradead.org, linux-btrfs@vger.kernel.org,
	lustre-devel@lists.lustre.org
Subject: Re: [PATCH 04/24] fs: Provide infrastructure for dynamic BDIs in filesystems
Date: Fri, 3 Feb 2017 10:31:56 -0800	[thread overview]
Message-ID: <20170203183155.GA30842@localhost.localdomain> (raw)
In-Reply-To: <20170203135042.GB5844@quack2.suse.cz>

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

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2017-02-03 18:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 17:33 [PATCH 0/24 RFC] fs: Convert all embedded bdis into separate ones Jan Kara
2017-02-02 17:34 ` [PATCH 04/24] fs: Provide infrastructure for dynamic BDIs in filesystems Jan Kara
2017-02-02 19:28   ` Liu Bo
2017-02-03 13:50     ` Jan Kara
2017-02-03 18:31       ` Liu Bo [this message]
     [not found]   ` <20170202173422.3240-5-jack-AlSwsSmVLrQ@public.gmane.org>
2017-02-08  0:38     ` Dilger, Andreas
     [not found]       ` <C01BF300-AD67-4A3E-810F-AAB2EEB90B97-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-02-09 12:12         ` Jan Kara
2017-02-02 17:34 ` [PATCH 19/24] nilfs2: Convert to properly refcounting bdi Jan Kara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170203183155.GA30842@localhost.localdomain \
    --to=bo.li.liu@oracle.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=cluster-devel@redhat.com \
    --cc=codalist@TELEMANN.coda.cs.cmu.edu \
    --cc=ecryptfs@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=lustre-devel@lists.lustre.org \
    --cc=osd-dev@open-osd.org \
    --cc=petr@vandrovec.name \
    --cc=v9fs-developer@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).