xfs-masters
[Top] [All Lists]

[xfs-masters] Re: [PATCH -mm 0/10][RFC] aio: make struct kiocb private

To: Nate Diller <nate.diller@xxxxxxxxx>
Subject: [xfs-masters] Re: [PATCH -mm 0/10][RFC] aio: make struct kiocb private
From: David Brownell <david-b@xxxxxxxxxxx>
Date: Tue, 16 Jan 2007 00:22:35 -0800
Cc: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxx>, Benjamin LaHaise <bcrl@xxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, Kenneth W Chen <kenneth.w.chen@xxxxxxxxx>, linux-aio@xxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Nate Diller <nate@xxxxxxxxx>, netdev@xxxxxxxxxxxxxxx, ocfs2-devel@xxxxxxxxxxxxxx, Suparna Bhattacharya <suparna@xxxxxxxxxx>, Trond Myklebust <trond.myklebust@xxxxxxxxxx>, xfs-masters@xxxxxxxxxxx
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=pacbell.net; h=Received:X-YMail-OSG:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id; b=IpX0h/9o5TvJ+2OlUQ2LNbDQHO9OJfIZ4RcmfD0LmKST/XfL36PMJiqA/EEjmarAxT8RKsJ7YIW0nSD4NDbItzhBch3raL5Gtx53eW7ZrXjP7BXyDhLeKDijq0HHcMxpkZNzmIH5ioZU498FLfxFfwYt/2UU/xXI4Hy+Q2EWPDg= ;
In-reply-to: <5c49b0ed0701152025t2e9fdd6cld36b077f36c78afe@xxxxxxxxxxxxxx>
References: <20070116015450.9764.37697.patchbomb.py@xxxxxxxxxxxxxxxxx> <20070116032347.GA3697@xxxxxxxxxxxxx> <5c49b0ed0701152025t2e9fdd6cld36b077f36c78afe@xxxxxxxxxxxxxx>
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
User-agent: KMail/1.7.1
On Monday 15 January 2007 8:25 pm, Nate Diller wrote:

> I don't think we should be waiting on sync I/O 
> at the *top* of the call stack, like with wait_on_sync_kiocb(), I'd
> say the best place to wait is at the *bottom*, down in the I/O
> scheduler.

Erm ... *what* I/O scheduler?  These I/O requests may go directly
to the end of the hardware I/O queue, which already has an I/O model
where each request can correspond directly to a KIOCB.  And which
does not include any synchronous primitives.

No such scheduler has previously been, or _should_ be, required.


<Prev in Thread] Current Thread [Next in Thread>