From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christophe Varoqui Subject: Re: [PATCH RFC 0/2] dm-mp netlink events Date: Wed, 9 Nov 2005 10:10:00 +0100 Message-ID: <20051109091000.GA16793@free.fr> References: <20051109075423.GA11492@us.ibm.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20051109075423.GA11492@us.ibm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: device-mapper development List-Id: dm-devel.ids On Tue, Nov 08, 2005 at 11:54:23PM -0800, Mike Anderson wrote: > This patch series creates a dm-mp hardware handler that sends netlink > messages when a hardware handlers error function is called. The skb > mempool in this patch is derived / copied from > drivers/scsi/scsi_transport_iscsi.c. > > Currently I have created this support in a hardware handler to reduce the > impact on other code, but this code could easily be moved to > dm-mpath.c::do_end_io or higher if desired. The events will also contain > better information once the scsi error mapping patches are done. > > This patch series contains: > 1 A hardware handler that sends events over netlink (dm-evt) > 2 A sample user space program to receive / display events. > (dm_evtd) > Would uevents work instead of yet another Netlink wire ? The multipath daemon already listens for uevents ... Regards, cvaroqui