From: David Vrabel <david.vrabel@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: <xen-devel@lists.xen.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH RFC 2/4] xen-blkfront: improve aproximation of required grants per request
Date: Thu, 11 Jul 2013 14:20:02 +0100 [thread overview]
Message-ID: <51DEB102.7060802@citrix.com> (raw)
In-Reply-To: <1373288607-1876-3-git-send-email-roger.pau@citrix.com>
On 08/07/13 14:03, Roger Pau Monne wrote:
> Improve the calculation of required grants to process a request by
> using nr_phys_segments instead of always assuming a request is going
> to use all posible segments.
This isn't obviously correct to me. Why is this correct value for the
number of pages that need to be granted?
David
> --- a/drivers/block/xen-blkfront.c
> +++ b/drivers/block/xen-blkfront.c
> @@ -400,10 +400,13 @@ static int blkif_queue_request(struct request *req)
> if (unlikely(info->connected != BLKIF_STATE_CONNECTED))
> return 1;
>
> - max_grefs = info->max_indirect_segments ?
> - info->max_indirect_segments +
> - INDIRECT_GREFS(info->max_indirect_segments) :
> - BLKIF_MAX_SEGMENTS_PER_REQUEST;
> + max_grefs = req->nr_phys_segments;
> + if (max_grefs > BLKIF_MAX_SEGMENTS_PER_REQUEST)
> + /*
> + * If we are using indirect segments we need to account
> + * for the indirect grefs used in the request.
> + */
> + max_grefs += INDIRECT_GREFS(req->nr_phys_segments);
>
> /* Check if we have enough grants to allocate a requests */
> if (info->persistent_gnts_c < max_grefs) {
next prev parent reply other threads:[~2013-07-11 13:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 13:03 [PATCH RFC 0/4] xen-block: prevent blkfront for hoarding grants Roger Pau Monne
2013-07-08 13:03 ` [PATCH RFC 1/4] xen-gnt: prevent adding duplicate gnt callbacks Roger Pau Monne
2013-07-11 13:17 ` [Xen-devel] " David Vrabel
2013-07-11 16:23 ` Roger Pau Monné
2013-07-08 13:03 ` [PATCH RFC 2/4] xen-blkfront: improve aproximation of required grants per request Roger Pau Monne
2013-07-11 13:20 ` David Vrabel [this message]
2013-07-11 14:47 ` [Xen-devel] " Roger Pau Monné
2013-07-08 13:03 ` [PATCH RFC 3/4] xen-blkfront: prevent hoarding all grants Roger Pau Monne
2013-07-11 13:32 ` [Xen-devel] " David Vrabel
2013-07-11 14:57 ` Roger Pau Monné
2013-07-08 13:03 ` [PATCH RFC 4/4] xen-block: introduce a new request type to unmap grants Roger Pau Monne
2013-07-08 19:41 ` Konrad Rzeszutek Wilk
2013-07-09 13:22 ` [Xen-devel] " Wei Liu
2013-07-09 16:37 ` Roger Pau Monné
2013-07-09 18:32 ` Konrad Rzeszutek Wilk
2013-07-09 18:38 ` [Xen-devel] " Wei Liu
2013-07-10 9:19 ` Roger Pau Monné
2013-07-10 13:54 ` [Xen-devel] " Egger, Christoph
2013-07-10 14:46 ` Roger Pau Monné
2013-07-10 14:52 ` Konrad Rzeszutek Wilk
2013-07-11 13:48 ` [Xen-devel] " David Vrabel
2013-07-11 15:12 ` Roger Pau Monné
2013-07-11 15:26 ` David Vrabel
2013-07-11 15:48 ` Roger Pau Monné
2013-07-12 10:12 ` David Vrabel
2013-07-11 13:35 ` [Xen-devel] [PATCH RFC 0/4] xen-block: prevent blkfront for hoarding grants David Vrabel
2013-07-31 9:50 ` Roger Pau Monné
2013-07-31 11:27 ` Konrad Rzeszutek Wilk
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=51DEB102.7060802@citrix.com \
--to=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).