[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a2b3147e-c542-b449-e69a-2dce050c29a6@redhat.com>
Date: Wed, 5 Oct 2016 15:30:49 -0700
From: Andy Grover <agrover@...hat.com>
To: 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 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
Powered by blists - more mailing lists