qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Wu Libin <gnlwlb@163.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Data classification in Qemu
Date: Wed, 17 Sep 2014 10:01:50 +0100	[thread overview]
Message-ID: <20140917090150.GA10699@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <4483414C-AE50-4371-944D-AED207A61E2C@163.com>

[-- Attachment #1: Type: text/plain, Size: 991 bytes --]

On Tue, Sep 16, 2014 at 11:03:04PM +0800, Wu Libin wrote:
> Yeah, i know dm-cache, it’s in the layer of block.
> 
> Maybe my description is not clear enough.Just because i see a patch, it will set flags which can classify IO size in bio->bi_flags, and in the function sd_prep_fn, it will set the SCSI command depends on the bio->bi_flags, like:
> SCpnt->cmnd[6] = DSS_BIO_CLASS(SCpnt->request->bio);
> 
> And i see the data classification function will be enabled when the device model is “QEMU”, so i guess the QEMU must can recognise the SCSI command. That’s why i will search the data classification about the QEMU.
> 
> It’s true QEMU not care about the filesystem, but we have flags, right, -:).

After a web search I guess you are are talking about this paper:
http://sigops.org/sosp/sosp11/current/2011-Cascais/printable/05-mesnier.pdf

The code isn't upstream and I've never heard of it.

I think you should get in touch with the authors instead.

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-09-17  9:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 16:06 [Qemu-devel] Data classification in Qemu Wu Libin
2014-09-16 14:46 ` Stefan Hajnoczi
2014-09-16 15:03   ` Wu Libin
2014-09-17  9:01     ` Stefan Hajnoczi [this message]
2014-09-17 13:48       ` Wu Libin

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=20140917090150.GA10699@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=gnlwlb@163.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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).