From: Rusty Russell <rusty@rustcorp.com.au>
To: Christoph Hellwig <hch@lst.de>,
qemu-devel@nongnu.org, linux-kernel@vger.kernel.org
Cc: stefanha@gmail.com, kwolf@redhat.com, prerna@linux.vnet.ibm.com,
aliguori@us.ibm.com
Subject: Re: [PATCH, RFC] virtio_blk: add cache control support
Date: Wed, 16 Mar 2011 14:39:39 +1030 [thread overview]
Message-ID: <87y64fhfjw.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20110315141644.GA30803@lst.de>
On Tue, 15 Mar 2011 15:16:44 +0100, Christoph Hellwig <hch@lst.de> wrote:
> Add support for the new dynamic features config space field to allow
> en/disabling the write cache at runtime. The userspace interface is
> a SCSI-compatible sysfs attribute.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Hi Christoph,
Neat work. Minor comments:
> + if (strncmp(buf, "write through", sizeof("write through") - 1) == 0) {
> + ;
> + } else if (strncmp(buf, "write back", sizeof("write back") - 1) == 0) {
Is there a reason we're not letting gcc and/or strcmp do the
optimization work here?
> + vdev->config->set(vdev, offsetof(struct virtio_blk_config, features),
> + &features, sizeof(features));
> +
> + vdev->config->get(vdev, offsetof(struct virtio_blk_config, features),
> + &features2, sizeof(features2));
> +
> + if ((features & VIRTIO_BLK_RT_WCE) !=
> + (features2 & VIRTIO_BLK_RT_WCE))
> + return -EIO;
This seems like a debugging check you left in. Or do you suspect
some issues?
Thanks,
Rusty.
next prev parent reply other threads:[~2011-03-16 4:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110315141049.GA30627@lst.de>
2011-03-15 14:16 ` [PATCH, RFC] virtio_blk: add cache control support Christoph Hellwig
2011-03-16 4:09 ` Rusty Russell [this message]
2011-03-16 14:09 ` Christoph Hellwig
2011-03-17 5:06 ` Rusty Russell
2011-03-17 14:21 ` [Qemu-devel] " Christoph Hellwig
2011-03-24 0:11 ` Rusty Russell
2011-03-24 3:11 ` Anthony Liguori
2011-03-24 3:05 ` Anthony Liguori
2011-03-24 9:54 ` Christian Borntraeger
2011-03-25 5:08 ` Rusty Russell
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=87y64fhfjw.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=aliguori@us.ibm.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prerna@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox