Re: Modifying blktrace to obtain i/o contents?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



OK, looks like we're not staying on the same ground in this discussion
:) What is the goal of you project? The answer to your question
depends on this.

Vasily

On Mon, Dec 19, 2011 at 3:25 PM, Vasily Tarasov <tarasov@xxxxxxxxxxx> wrote:
> OK, looks like we're not staying on the same ground in this discussion :)
> What is the goal of you project? The answer to your question depends on
> this.
>
> Thank you,
> Vasily
>
>
> On Thu, Dec 15, 2011 at 9:24 AM, Sushil Mantri <sushilmantri@xxxxxxxxx>
> wrote:
>>
>> Hi,
>>
>> Sorry i couldn't reply back as I was busy with my finals :) . I looked a
>> bit into device mapper, and feel it could work, but since i have looked into
>> blktrace already i will take that approach. For now, i need the contents,
>> but i am wondering why obtaining hash using blktrace is a good idea and not
>> the contents itself. I will obtain contents as i mentioned in my first
>> message.
>>
>> Thanks for your replies
>>
>>
>> On Tue, Dec 13, 2011 at 1:06 PM, Vasily Tarasov <tarasov@xxxxxxxxxxx>
>> wrote:
>>>
>>> >
>>> > Yes, I guess that might be the case. The subject said "i/o contents" so
>>> > I'd assumed that he wanted the complete data rather than just a hash.
>>> > Apologies if I've misunderstood that.
>>> >
>>> > Even so, since there are generic tracepoints now, a small device mapper
>>> > target could produce that information in exactly the same way as
>>> > blktrace and remain modular. It would also be able to modify the i/o
>>> > too, which I assumed was the eventual aim,
>>> >
>>> > Steve.
>>> >
>>>
>>> Right, dm target would be modular, but he would need to implement
>>> certain amount of code for efficient export of trace to the
>>> user-space. Blktrace has implemented it already (and user-space part
>>> is ready as well), so he would not need to do it. However, if there is
>>> already a generic way in kernel to export a lot of data to user-space
>>> efficiently, then dm might work as well. And, of course, if dedup
>>> itself (not trace) is a final goal - then I agree completely - dm
>>> target sounds like a good point.
>>>
>>> Vasily
>>
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrace" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Netdev]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux