Re: [rfc] direct IO submission and completion scalability issues

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Nick Piggin <npiggin@...>
Cc: Siddha, Suresh B <suresh.b.siddha@...>, <linux-kernel@...>, <arjan@...>, <mingo@...>, <ak@...>, <jens.axboe@...>, <James.Bottomley@...>, <andrea@...>, <clameter@...>, <akpm@...>, <andrew.vasquez@...>, <willy@...>, Zach Brown <zach.brown@...>
Date: Monday, February 4, 2008 - 6:30 am

> +	q = &__get_cpu_var(call_single_queue);

I think you could do that lockless if you use a similar data structure
as netchannels (essentially a fixed size single buffer queue with atomic 
exchange of the first/last pointers) and not using a list. That would avoid 
at least one bounce for the lock and likely another one for the  list
manipulation.

Also the right way would be to not add a second mechanism for this,
but fix the standard smp_call_function_single() to support it.

-Andi
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[rfc] direct IO submission and completion scalability issues, Siddha, Suresh B, (Fri Jul 27, 9:21 pm)
Re: [rfc] direct IO submission and completion scalability is..., Andi Kleen, (Mon Feb 4, 6:30 am)
Re: [rfc] direct IO submission and completion scalability is..., Christoph Lameter, (Mon Jul 30, 2:20 pm)