Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759285AbYAJWd0 (ORCPT ); Thu, 10 Jan 2008 17:33:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758384AbYAJWdN (ORCPT ); Thu, 10 Jan 2008 17:33:13 -0500 Received: from py-out-1112.google.com ([64.233.166.180]:23926 "EHLO py-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757596AbYAJWdL (ORCPT ); Thu, 10 Jan 2008 17:33:11 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:from; b=JL00vCsewvvrBwPMi/YQDhGq7lLF+RtZYhfUUN8HkCJSYALrervBXlgfpKU/JrRCecwMAUL4v/yhFgewc1IxKclw2sPl9Idv+kqRQFFzlAMpZlEcVXLS06/Ug95cyK+Klcs+73NWyouak+su/FnCiyp+v65un119ieF0WC3TqnM= Cc: James Bottomley , FUJITA Tomonori , tomof@acm.org, deepakrc@gmail.com, linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org Message-Id: <622A3567-4665-48DE-8C2C-B9297BBD9A83@gmail.com> To: Pete Wyckoff In-Reply-To: <20080110214605.GD1928@osc.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Subject: Re: [PATCH] bsg : Add support for io vectors in bsg Date: Thu, 10 Jan 2008 16:33:07 -0600 References: <200801050501.m0551LFB030667@mbox.iij4u.or.jp> <20080108220918.GA9484@osc.edu> <20080109091118N.fujita.tomonori@lab.ntt.co.jp> <20080110204325.GC1928@osc.edu> <1199998531.3141.96.camel@localhost.localdomain> <20080110214605.GD1928@osc.edu> X-Mailer: Apple Mail (2.915) From: Mark Rustad Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1319 Lines: 32 On Jan 10, 2008, at 3:46 PM, Pete Wyckoff wrote: > I'm fine with read/write, except Tomo is against handling iovecs > because of the compat complexity with struct iovec being different > on 32- vs 64-bit. There is a standard way to do "compat" ioctl that > hides this handling in a different file (not bsg.c), which is the > only reason I'm even considering these ioctls. I don't care about > compat setups per se. That is what I was thinking. Is it really necessary to support something like bsg for 32 on 64 bit? Yes, it is a userspace interface, but it isn't the kind of thing that normal user programs would use. It is a new interface for newly-written programs and I would expect those to be native. At least it doesn't strike me as overly-restrictive for that to be the case for this kind of interface. > Is there another async I/O mechanism? Userspace builds the CDBs, > just needs some way to drop them in SCSI ML. BSG is almost perfect > for this, but doesn't do iovec, leading to lots of memcpy. Precisely. -- Mark Rustad, MRustad@gmail.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/