[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bfdd6f56-ce2b-ef74-27b1-83b922e5f7d9@suse.de>
Date: Wed, 23 Jun 2021 14:03:27 +0200
From: Hannes Reinecke <hare@...e.de>
To: Matteo Croce <mcroce@...ux.microsoft.com>,
linux-block@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Jens Axboe <axboe@...nel.dk>
Cc: linux-kernel@...r.kernel.org,
Lennart Poettering <lennart@...ttering.net>,
Luca Boccassi <bluca@...ian.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
Damien Le Moal <damien.lemoal@....com>,
Tejun Heo <tj@...nel.org>,
Javier González <javier@...igon.com>,
Niklas Cassel <niklas.cassel@....com>,
Johannes Thumshirn <johannes.thumshirn@....com>,
Matthew Wilcox <willy@...radead.org>,
Christoph Hellwig <hch@...radead.org>,
JeffleXu <jefflexu@...ux.alibaba.com>
Subject: Re: [PATCH v3 0/6] block: add a sequence number to disks
On 6/23/21 12:58 PM, Matteo Croce wrote:
> From: Matteo Croce <mcroce@...rosoft.com>
>
> With this series a monotonically increasing number is added to disks,
> precisely in the genhd struct, and it's exported in sysfs and uevent.
>
> This helps the userspace correlate events for devices that reuse the
> same device, like loop.
>
I'm failing to see the point here.
Apparently you are assuming that there is a userspace tool tracking
events, and has a need to correlate events related to different
instances of the disk.
But if you have an userspace application tracking events, why can't the
same application track the 'add' and 'remove' events to track the
lifetime of the devices, and implement its own numbering based on that?
Why do we need to burden the kernel with this?
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@...e.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Powered by blists - more mailing lists