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?
If not we could probably aim for per-cpu queues using blk-mq and a
socket per cpu or similar.
First, a disclaimer--I haven't really been following this discussion
very closely.
For an rbd image request (which is what gets created from requests
from the block queue), the order of completion doesn't matter, and
although the object requests are submitted in order that shouldn't
be required either.
The image request is broken into one or more object requests (usually
just one) and they are treated as a unit. When the last object request
of a set for an image request has completed, the image request is
treated as completed.
I hope that helps. If not, ask again a different way...
-Alex
--
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
