Re: Trapping Block I/O

On Fri, Sep 23 2005, Fawad Lateef wrote:
> you created wrapper .... So by doing this you can easily monitor
> requests (similar to this approach is used in LVM/RAID) ......

Or just use btrace, pull it from:

git://brick.kernel.dk/data/git/blktrace.git

-- 
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Trapping Block I/O
    • From: Fawad Lateef <[email protected]>

• References:
  • Trapping Block I/O
    • From: Block Device <[email protected]>
  • Re: Trapping Block I/O
    • From: Fawad Lateef <[email protected]>

• Prev by Date: Re: [patch] Make epoll_wait() handle negative timeouts as MAX_SCHEDULE_TIMEOUT ...
• Next by Date: Re: [PATCH 0/3] netfilter : 3 patches to boost ip_tables performance
• Previous by thread: Re: Trapping Block I/O
• Next by thread: Re: Trapping Block I/O
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]