qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Liu Yuan <namei.unix@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	sheepdog@lists.wpkg.org, qemu-devel@nongnu.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Subject: Re: [Qemu-devel] [PATCH v7] sheepdog: add discard/trim support for sheepdog
Date: Thu, 18 Apr 2013 15:41:20 +0800	[thread overview]
Message-ID: <516FA3A0.1030002@gmail.com> (raw)
In-Reply-To: <20130418073712.GC19195@stefanha-thinkpad.redhat.com>

On 04/18/2013 03:37 PM, Stefan Hajnoczi wrote:
>> @@ -184,6 +186,8 @@ typedef struct SheepdogInode {
>> >      uint32_t data_vdi_id[MAX_DATA_OBJS];
>> >  } SheepdogInode;
>> >  
>> > +static bool discard_supported = true;
> Normally state should be part of BDRVSheepdogState so that it does not
> affect other sheepdog drives.
> 
> Please confirm that all -drive file=sheepdog:... must either support
> discard or not support it.  I asked this in an older version of the
> patch but wasn't sure if my question was clear.
> 

Ah, I see, this time I got your question clearly.

> Imagine a scenario where you run two sheepdog clusters and want to
> connect one drive from each cluster to your VM.  If one cluster uses
> outdated sheepdog software but the other is up-to-date, then it should
> still be possible to use discard on the up-to-date cluster.

Makes sense. I'll use a per structure enabler.

Thanks,
Yuan

  reply	other threads:[~2013-04-18  7:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18  5:44 [Qemu-devel] [PATCH v6] sheepdog: add discard/trim support for sheepdog Liu Yuan
2013-04-18  5:50 ` [Qemu-devel] [PATCH v7] " Liu Yuan
2013-04-18  7:37   ` Stefan Hajnoczi
2013-04-18  7:41     ` Liu Yuan [this message]
2013-04-18  8:24 ` [Qemu-devel] [PATCH v8] " Liu Yuan
2013-04-18 11:05   ` Stefan Hajnoczi

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=516FA3A0.1030002@gmail.com \
    --to=namei.unix@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=morita.kazutaka@lab.ntt.co.jp \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sheepdog@lists.wpkg.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).