linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Singh, Balbir" <sblbir@amazon.com>
To: "hch@lst.de" <hch@lst.de>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
	"Chaitanya.Kulkarni@wdc.com" <Chaitanya.Kulkarni@wdc.com>,
	"mst@redhat.com" <mst@redhat.com>,
	"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"Sangaraju,  Someswarudu" <ssomesh@amazon.com>
Subject: Re: [resend v1 1/5] block/genhd: Notify udev about capacity change
Date: Tue, 21 Jan 2020 19:57:18 +0000	[thread overview]
Message-ID: <a1a36b7163c10fd6c9450ba631f26b9ce23dc3f7.camel@amazon.com> (raw)
In-Reply-To: <20200108150428.GB10975@lst.de>

On Wed, 2020-01-08 at 16:04 +0100, hch@lst.de wrote:
> On Tue, Jan 07, 2020 at 10:15:34PM -0500, Martin K. Petersen wrote:
> > 
> > Balbir,
> > 
> > > I did this to avoid having to enforce that set_capacity() implied a
> > > notification. Largely to control the impact of the change by default.
> > 
> > What I thought. I'm OK with set_capacity_and_notify(), btw.
> 
> To some extent it might make sense to always notify from set_capacity
> and have a set_capacity_nonotify if we don't want to notify, as in
> general we probably should notify unless we have a good reason not to.

I am not sure if this is the right path, since with the new interface, we'll
now have revalidate disk bits built into the function (see the comments from
Bob earlier). I'd be happier converting interfaces a few at a time, A quick
grep found over 100 references and I am not even sure how many of them are
resizable without hotplug in/out on the fly. Hence, I limited myself to the
small subset, I could consider expanding it later based on the need and their
ability to resize on the fly

Balbir Singh.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2020-01-21 19:57 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02  7:53 [resend v1 0/5] Add support for block disk resize notification Balbir Singh
2020-01-02  7:53 ` [resend v1 1/5] block/genhd: Notify udev about capacity change Balbir Singh
2020-01-03  6:16   ` Chaitanya Kulkarni
2020-01-04  4:44     ` Singh, Balbir
2020-01-04 22:32       ` Chaitanya Kulkarni
2020-01-08 15:02     ` hch
2020-01-07  3:32   ` Martin K. Petersen
2020-01-07 22:30     ` Singh, Balbir
2020-01-08  3:15       ` Martin K. Petersen
2020-01-08 15:04         ` hch
2020-01-21 19:57           ` Singh, Balbir [this message]
2020-01-02  7:53 ` [resend v1 2/5] drivers/block/virtio_blk.c: Convert to use disk_set_capacity Balbir Singh
2020-01-02  7:53 ` [resend v1 3/5] drivers/block/xen-blkfront.c: " Balbir Singh
2020-01-02  7:53 ` [resend v1 4/5] drivers/nvme/host/core.c: " Balbir Singh
2020-01-04 22:27   ` Chaitanya Kulkarni
2020-01-06  0:46     ` Singh, Balbir
2020-01-08 15:04       ` hch
2020-01-09  3:33         ` Martin K. Petersen
2020-01-09 13:12           ` Ewan D. Milne
2020-01-21 19:52         ` Singh, Balbir
2020-01-02  7:53 ` [resend v1 5/5] drivers/scsi/sd.c: " Balbir Singh
2020-01-02 22:21   ` Chaitanya Kulkarni
2020-01-03  0:23     ` Singh, Balbir
2020-01-07  3:48   ` Martin K. Petersen
2020-01-07  3:57     ` James Bottomley
2020-01-07  4:39       ` Martin K. Petersen
2020-01-07 21:37         ` Ewan D. Milne
2020-01-08  2:59           ` Martin K. Petersen
2020-01-08 21:27             ` Ewan D. Milne
2020-01-07 22:28     ` Singh, Balbir
2020-01-08  3:15       ` Martin K. Petersen
2020-01-08  4:20         ` Singh, Balbir
2020-01-08 21:32         ` Ewan D. Milne
2020-01-08 15:06     ` Christoph Hellwig
2020-01-09  2:53       ` Martin K. Petersen
2020-01-06  5:59 ` [resend v1 0/5] Add support for block disk resize notification Bob Liu
2020-01-06  8:47   ` Singh, Balbir
2020-01-06  9:08     ` Bob Liu

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=a1a36b7163c10fd6c9450ba631f26b9ce23dc3f7.camel@amazon.com \
    --to=sblbir@amazon.com \
    --cc=Chaitanya.Kulkarni@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=jejb@linux.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=martin.petersen@oracle.com \
    --cc=mst@redhat.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 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).