Subject: Re: [dm-devel] [PATCH 0/9] Generate uevents for all DM events
To: Greg KH <gregkh@linuxfoundation.org>, dm-devel@redhat.com,
        linux-kernel@vger.kernel.org, snitzer@redhat.com
References: <1475522580-16723-1-git-send-email-agrover@redhat.com>
 <20161004072015.GA11216@kroah.com>
 <fe185eba-f802-6731-8da7-736c117db135@redhat.com>
 <20161005004004.GC28416@agk-dp.fab.redhat.com>
 <20161005065101.GB11013@kroah.com>
 <0afb2645-59e5-f9a6-ca1f-29aaadf59400@redhat.com>
 <20161005174358.GD28416@agk-dp.fab.redhat.com>
From: Andy Grover <agrover@redhat.com>
Organization: Red Hat
Message-ID: <a2b3147e-c542-b449-e69a-2dce050c29a6@redhat.com>
Date: Wed, 5 Oct 2016 15:30:49 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <20161005174358.GD28416@agk-dp.fab.redhat.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 958
Lines: 20

On 10/05/2016 10:43 AM, Alasdair G Kergon wrote:
> 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.

Yeah just like Hannes said, I just want to get dm events for multiple dm 
devices without burning a thread for each device. After your 
clarification, netlink seems like the best option and not overkill.

Give me a few days and I can have something for you to review.

Thanks -- Regards -- Andy