From owner-freebsd-arch@FreeBSD.ORG Thu Jan 26 00:08:00 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 457C316A420; Thu, 26 Jan 2006 00:07:58 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <43D812F7.50808@freebsd.org> Date: Thu, 26 Jan 2006 08:08:23 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20060117 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <43D6C3A5.4060100@freebsd.org> <86k6coodch.fsf@xps.des.no> In-Reply-To: <86k6coodch.fsf@xps.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: arch@freebsd.org Subject: Re: vfs_aio.c is still not safe X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2006 00:08:00 -0000 Dag-Erling Smørgrav wrote: >3) Rewrite the aio code to use kthreads attached to each process, so > problems with one process's aio does not propagate to other > processes. > > > This is not a complete solution, it shifts the problem to another side, allow user to kill process. >DES > >