Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934182AbcJERoF (ORCPT ); Wed, 5 Oct 2016 13:44:05 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57496 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932863AbcJERoB (ORCPT ); Wed, 5 Oct 2016 13:44:01 -0400 Date: Wed, 5 Oct 2016 18:43:58 +0100 From: Alasdair G Kergon To: Andy Grover Cc: Greg KH , dm-devel@redhat.com, linux-kernel@vger.kernel.org, snitzer@redhat.com Subject: Re: [dm-devel] [PATCH 0/9] Generate uevents for all DM events Message-ID: <20161005174358.GD28416@agk-dp.fab.redhat.com> Mail-Followup-To: Andy Grover , Greg KH , 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> <20161005004004.GC28416@agk-dp.fab.redhat.com> <20161005065101.GB11013@kroah.com> <0afb2645-59e5-f9a6-ca1f-29aaadf59400@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0afb2645-59e5-f9a6-ca1f-29aaadf59400@redhat.com> Organization: Red Hat UK Ltd. Registered in England and Wales, number 03798903. Registered Office: Peninsular House, 30-36 Monument Street, 4th Floor, London, England, EC3R 8NB. User-Agent: Mutt/1.5.18 (2008-05-17) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Wed, 05 Oct 2016 17:44:00 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 613 Lines: 13 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