[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <g6xw3whylji5t7k79aUYAxe124vaj_firegpg@mail.gmail.com>
Date: Thu, 18 Mar 2010 11:23:53 -0700 (PST)
From: drepper@...il.com
To: Ingo Molnar <mingo@...e.hu>
Cc: Anthony Liguori <anthony@...emonkey.ws>,
Avi Kivity <avi@...hat.com>,
"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Sheng Yang <sheng@...ux.intel.com>,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
Marcelo Tosatti <mtosatti@...hat.com>,
oerg Roedel <joro@...tes.org>,
Jes Sorensen <Jes.Sorensen@...hat.com>,
Gleb Natapov <gleb@...hat.com>,
Zachary Amsden <zamsden@...hat.com>, ziteng.huang@...el.com,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Fr?d?ric Weisbecker <fweisbec@...il.com>
Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single project
On Thu, Mar 18, 2010 at 09:13, Ingo Molnar <mingo@...e.hu> wrote:
> The suckage of kernel async IO is for similar reasons: there's an ugly package
> separation problem between the kernel and between glibc
Bollocks. glibc would use (and is using) everything the kernel provides. We even have an implementation using the current AIO code. It only works in some situations but that's what the few users are OK with.
Don't try to blame anyone but kernel people for the complete and utter failure of AIO in Linux. I don't know how often I've discussed design of a kernel interface with various kernel developers. Heck, whenever Zach Brown and I meet there never is a different topic. And following these meetings the ball is not and cannot be in my court. How could it?
Download attachment "signature.asc" of type "application/pgp-signature" (273 bytes)
Powered by blists - more mailing lists