From: Alex Elder <elder@ieee.org>
To: Christoph Hellwig <hch@infradead.org>,
Alexandre DERUMIER <aderumier@odiso.com>
Cc: Ceph Devel <ceph-devel@vger.kernel.org>
Subject: Re: krbd blk-mq support ?
Date: Tue, 28 Oct 2014 18:11:08 -0500 [thread overview]
Message-ID: <5450228C.3010907@ieee.org> (raw)
In-Reply-To: <20141028180725.GA1138@infradead.org>
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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-10-28 23:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9894b2d1-b7c6-4a17-9747-d8a41ec208a4@mailpro>
2014-10-24 7:54 ` krbd blk-mq support ? Alexandre DERUMIER
2014-10-24 8:41 ` Ilya Dryomov
2014-10-24 10:55 ` Christoph Hellwig
2014-10-24 12:27 ` Alexandre DERUMIER
2014-10-26 13:46 ` Alexandre DERUMIER
2014-10-26 19:08 ` Somnath Roy
2014-10-27 7:53 ` Alexandre DERUMIER
2014-10-27 10:26 ` Alexandre DERUMIER
2014-10-27 9:45 ` Christoph Hellwig
2014-10-27 10:00 ` Alexandre DERUMIER
2014-10-28 18:07 ` Christoph Hellwig
2014-10-28 22:31 ` Alex Elder
2014-10-28 23:11 ` Alex Elder [this message]
2014-10-29 9:09 ` Alexandre DERUMIER
2014-10-29 15:00 ` Sage Weil
2014-10-30 8:11 ` Alexandre DERUMIER
2014-10-30 16:01 ` Alexandre DERUMIER
2014-10-30 17:05 ` Haomai Wang
2014-10-31 5:04 ` Alexandre DERUMIER
2014-11-03 11:08 ` Christoph Hellwig
2014-11-03 13:08 ` Alexandre DERUMIER
[not found] <90C9DE11-CACE-4533-83EF-6F1F887E6A8F@profihost.ag>
2014-10-31 20:12 ` Alexandre DERUMIER
[not found] <100ed8b3-2427-46d0-9a0c-e5e1a92031af@mailpro>
2014-11-04 7:19 ` Alexandre DERUMIER
2014-11-13 7:18 ` Christoph Hellwig
2014-11-13 9:44 ` Alexandre DERUMIER
2014-12-10 14:05 ` Christoph Hellwig
[not found] ` <1394621476.865737.1418231736651.JavaMail.zimbra@oxygem.tv>
2014-12-10 17:15 ` Alexandre DERUMIER
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5450228C.3010907@ieee.org \
--to=elder@ieee.org \
--cc=aderumier@odiso.com \
--cc=ceph-devel@vger.kernel.org \
--cc=hch@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.