From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alasdair G Kergon Subject: Re: [PATCH] reworked dm-switch target Date: Tue, 21 Aug 2012 19:14:32 +0100 Message-ID: <20120821181432.GA32051@agk-dp.fab.redhat.com> References: <20120816070955.GA32526@agk-dp.fab.redhat.com> <20120821163329.GA21395@freewill.lab.equallogic.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20120821163329.GA21395@freewill.lab.equallogic.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 Cc: Mikulas Patocka , Jason_Shamberger@dell.com, Kevin_OKelley@dell.com List-Id: dm-devel.ids Well my order of preference for the interface at the moment would be: ioctl: ASCII dm messages ioctl: binary dm messages (i.e. the message content is treated as a binary blob) mmap: lookups in shared memory (lockless preferably) netlink Alasdair