Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933650AbZDASqU (ORCPT ); Wed, 1 Apr 2009 14:46:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933612AbZDASpo (ORCPT ); Wed, 1 Apr 2009 14:45:44 -0400 Received: from wa-out-1112.google.com ([209.85.146.178]:23970 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933581AbZDASpl (ORCPT ); Wed, 1 Apr 2009 14:45:41 -0400 Message-ID: <49D3B64F.6070703@codemonkey.ws> Date: Wed, 01 Apr 2009 13:45:35 -0500 From: Anthony Liguori User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Andi Kleen CC: Gregory Haskins , linux-kernel@vger.kernel.org, agraf@suse.de, pmullaney@novell.com, pmorreale@novell.com, rusty@rustcorp.com.au, netdev@vger.kernel.org, kvm@vger.kernel.org Subject: Re: [RFC PATCH 00/17] virtual-bus References: <20090331184057.28333.77287.stgit@dev.haskins.net> <87ab71monw.fsf@basil.nowhere.org> <49D35825.3050001@novell.com> <20090401132340.GT11935@one.firstfloor.org> <49D37805.1060301@novell.com> <20090401170103.GU11935@one.firstfloor.org> In-Reply-To: <20090401170103.GU11935@one.firstfloor.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1286 Lines: 35 Andi Kleen wrote: > On Wed, Apr 01, 2009 at 10:19:49AM -0400, Gregory Haskins wrote: > >>>> >>>> >>> But surely you must have some specific use case in mind? Something >>> that it does better than the various methods that are available >>> today. Or rather there must be some problem you're trying >>> to solve. I'm just not sure what that problem exactly is. >>> >>> >> Performance. We are trying to create a high performance IO infrastructure. >> > > Ok. So the goal is to bypass user space qemu completely for better > performance. Can you please put this into the initial patch > description? > FWIW, there's nothing that prevents in-kernel back ends with virtio so vbus certainly isn't required for in-kernel backends. That said, I don't think we're bound today by the fact that we're in userspace. Rather we're bound by the interfaces we have between the host kernel and userspace to generate IO. I'd rather fix those interfaces than put more stuff in the kernel. Regards, Anthony Liguori -- 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/