On 10/28/2014 01:07 PM, Christoph Hellwig wrote:
On Mon, Oct 27, 2014 at 11:00:46AM +0100, Alexandre DERUMIER wrote:
Can you do a perf report -ag and then a perf report to see where these
cycles are spent?
Yes, sure.
I have attached the perf report to this mail.
(This is with kernel 3.14, don't have access to my 3.18 host for now)
Oh, that's without the blk-mq patch?
Either way the profile doesn't really sum up to a fully used up
cpu. Sage, Alex - are there any ordring constraints in the rbd client?
I don't remember off hand.
In libceph I recall going to great lengths to retain the original
order of requests when they got re-sent after a connection reset.
I'll go look at the code a bit and see if I can refresh my memory
(though Sage may answer before I do).
-Alex
If not we could probably aim for per-cpu queues using blk-mq and a
socket per cpu or similar.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
