[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161005174358.GD28416@agk-dp.fab.redhat.com>
Date: Wed, 5 Oct 2016 18:43:58 +0100
From: Alasdair G Kergon <agk@...hat.com>
To: Andy Grover <agrover@...hat.com>
Cc: Greg KH <gregkh@...uxfoundation.org>, dm-devel@...hat.com,
linux-kernel@...r.kernel.org, snitzer@...hat.com
Subject: Re: [dm-devel] [PATCH 0/9] Generate uevents for all DM events
On Wed, Oct 05, 2016 at 10:06:41AM -0700, Andy Grover wrote:
> My project *would* like this added sooner, so I'll work on a revised
> patchset that uses netlink instead of uevents, and will also work on a
> revision to uevents.txt that talks about KOBJ_CHANGE and when it should
> and should not be used, as described by agk, to help out the next person.
netlink might still be overkill for this at this stage, if it's only
making one thread able to monitor multiple devices efficiently.
Let's find out your requirements and see if there's anything different from
the ones we've debated before.
Alasdair
Powered by blists - more mailing lists