From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH] xen/blkback: add xen-blkback support
Date: Mon, 18 Apr 2011 14:12:11 -0400 [thread overview]
Message-ID: <20110418181211.GA1149@dumpdata.com> (raw)
In-Reply-To: <1303149464-875-2-git-send-email-konrad.wilk@oracle.com>
Talk about self-review :-)
> index 90f22cc..9b60e69 100644
> --- a/block/blk-core.c
> +++ b/block/blk-core.c
> @@ -351,6 +351,7 @@ void blk_put_queue(struct request_queue *q)
> {
> kobject_put(&q->kobj);
> }
> +EXPORT_SYMBOL_GPL(blk_put_queue);
>
> /*
> * Note: If a driver supplied the queue lock, it should not zap that lock
> @@ -572,6 +573,7 @@ int blk_get_queue(struct request_queue *q)
>
> return 1;
> }
> +EXPORT_SYMBOL_GPL(blk_get_queue);
>
.. snip..
> +static void dispatch_rw_block_io(struct blkif_st *blkif,
.. snip..
> + struct request_queue *q;
.. snip
> + q = bdev_get_queue(preq.bdev);
> + if (!q)
> + goto fail_response;
.. snip..
> + /* Get a reference count for the disk queue and start sending I/O */
> + blk_get_queue(q);
> + blk_start_plug(&plug);
> +
> + for (i = 0; i < nbio; i++)
> + submit_bio(operation, biolist[i]);
> +
> + blk_finish_plug(&plug);
> + /* Let the I/Os go.. */
> + blk_put_queue(q);
Hmm, let me remove those get/puts. They are actually not necessary as we
already hold a reference count when we opened the device.
next prev parent reply other threads:[~2011-04-18 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 17:57 [RFC PATCH] Xen blkback for 2.6.40 Konrad Rzeszutek Wilk
2011-04-18 17:57 ` [PATCH] xen/blkback: add xen-blkback support Konrad Rzeszutek Wilk
2011-04-18 18:12 ` Konrad Rzeszutek Wilk [this message]
2011-04-18 18:31 ` Daniel Stodden
2011-04-18 20:14 ` Konrad Rzeszutek Wilk
2011-04-18 18:37 ` [RFC PATCH] Xen blkback for 2.6.40 Daniel Stodden
2011-04-18 20:12 ` 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=20110418181211.GA1149@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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.