From: "hch@lst.de" <hch@lst.de>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Cc: "sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"axboe@fb.com" <axboe@fb.com>,
"Sangaraju, Someswarudu" <ssomesh@amazon.com>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"Singh, Balbir" <sblbir@amazon.com>, "hch@lst.de" <hch@lst.de>
Subject: Re: [RFC][PATCH] nvme/core: Notify udev about capacity change
Date: Tue, 3 Dec 2019 08:34:47 +0100 [thread overview]
Message-ID: <20191203073447.GA23426@lst.de> (raw)
In-Reply-To: <BYAPR04MB57497F5F024F3E5F2200835F86420@BYAPR04MB5749.namprd04.prod.outlook.com>
On Tue, Dec 03, 2019 at 07:26:03AM +0000, Chaitanya Kulkarni wrote:
> On 12/02/2019 10:54 PM, hch@lst.de wrote:
> > I pretty much hate the set_capacity name to start with, so what about
> > a more descriptive name for new the helper? blk_set_capacity?
>
> Do we also need a blk_mq_ops or appropriate block layer callback
> capacity change function, so that file systems can register
> a callback function to take an appropriate action, e.g.
> rebuilding the metadata with new size ?
>
> If this make sense I'll be happy to take a look.
Well, and op isn't going to help with file system notifications as
that goes the other way around. We'd probably need some way how
file systems can register a new callback into the existing block
device events framework that is used for media changes.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-12-03 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 0:27 [RFC][PATCH] nvme/core: Notify udev about capacity change Balbir Singh
2019-11-29 8:24 ` Christoph Hellwig
2019-12-02 23:35 ` Singh, Balbir
2019-12-03 6:54 ` hch
2019-12-03 7:26 ` Chaitanya Kulkarni
2019-12-03 7:34 ` hch [this message]
2019-12-03 12:43 ` Johannes Thumshirn
2019-12-03 12:52 ` hch
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=20191203073447.GA23426@lst.de \
--to=hch@lst.de \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=axboe@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=sblbir@amazon.com \
--cc=ssomesh@amazon.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.