Linux btrace development
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: linux-btrace@vger.kernel.org
Subject: Re: Modifying blktrace to obtain i/o contents?
Date: Mon, 12 Dec 2011 17:05:52 +0000	[thread overview]
Message-ID: <1323709552.2729.24.camel@menhir> (raw)
In-Reply-To: <CAFFtA87hHc9cG8qawFaYsF2P9aYBqaBsJyKkXFV2utxOrUVNDQ@mail.gmail.com>

Hi,

On Mon, 2011-12-12 at 12:00 -0500, Sushil Mantri wrote:
> Hi,
> 
> I am working on de-duplication, for which i need the i/o event traces
> along with its contents. I have been looking into blktrace kernel code
> for some time, and have thought of a hacky solution to start with. In
> all the probe functions where i have "bio" struct i could obtain the
> "contents" from it, and write that in the relay channel as well. The
> blkparser would have to be modified as well to take this change into
> account.
> 
> Do you guys think i might be missing something or is there an
> alternative way to handle this?
> 
> Thanks,
> Sushil

I don't think that is probably a good way to do deduplication. Have you
considered just writing a device mapper target for this? Thats probably
the best way to do it,

Steve.




  reply	other threads:[~2011-12-12 17:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 17:00 Modifying blktrace to obtain i/o contents? Sushil Mantri
2011-12-12 17:05 ` Steven Whitehouse [this message]
2011-12-12 20:18 ` Vasily Tarasov
2011-12-13  9:17 ` Steven Whitehouse
2011-12-13 18:06 ` Vasily Tarasov
2011-12-15 14:25 ` Sushil Mantri
2011-12-19 21:06 ` Vasily Tarasov
2012-01-11 16:27 ` Alireza Haghdoost

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=1323709552.2729.24.camel@menhir \
    --to=swhiteho@redhat.com \
    --cc=linux-btrace@vger.kernel.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