On 12/03/2012 08:52 PM, Dave Chinner wrote:
> On Mon, Dec 03, 2012 at 10:59:39AM -0600, Dave Kleikamp wrote:
>> On 11/22/2012 05:06 PM, Dave Chinner wrote:
>>> And this extra fsync is now not done in the aio path. I.e. the AIO
>>> completion path needs to issue the fsync to maintain correct REQ_FU
On Mon, Dec 03, 2012 at 10:59:39AM -0600, Dave Kleikamp wrote:
> On 11/22/2012 05:06 PM, Dave Chinner wrote:
> > On Wed, Nov 21, 2012 at 04:40:56PM -0600, Dave Kleikamp wrote:
> >> From: Zach Brown
> >>
> >> This uses the new kernel aio interface to process loopback IO by
> >> submitting concurren
On 11/22/2012 05:06 PM, Dave Chinner wrote:
> On Wed, Nov 21, 2012 at 04:40:56PM -0600, Dave Kleikamp wrote:
>> From: Zach Brown
>>
>> This uses the new kernel aio interface to process loopback IO by
>> submitting concurrent direct aio. Previously loop's IO was serialized
>> by synchronous proces
On Wed, Nov 21, 2012 at 04:40:56PM -0600, Dave Kleikamp wrote:
> From: Zach Brown
>
> This uses the new kernel aio interface to process loopback IO by
> submitting concurrent direct aio. Previously loop's IO was serialized
> by synchronous processing in a thread.
>
> The aio operations specify
From: Zach Brown
This uses the new kernel aio interface to process loopback IO by
submitting concurrent direct aio. Previously loop's IO was serialized
by synchronous processing in a thread.
The aio operations specify the memory for the IO with the bio_vec arrays
directly instead of mappings of
5 matches
Mail list logo