[8946] in linux-scsi channel archive
Re: scsi buffer head write capturing
daemon@ATHENA.MIT.EDU (P.Basker)
Mon Jun 5 01:45:00 2000
Date: Mon, 5 Jun 2000 11:12:25 +0530 (IST)
From: "P.Basker" <basker_p@bbv.satyam.com>
To: Eric Youngdale <eric@andante.org>
Cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <00f001bfcda6$13ff31e0$0f17a8c0@eric.home>
Message-ID: <Pine.LNX.4.21.0006051104480.936-100000@archimedes.bbv.satyam.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hi eric,
Im actually viewing the buffer blocks that are written to the
disk in each flush from the buffer cache. I capture the request function
of the scsi device( do_sd_request() ) and invoke my own routine before
actually calling the old routine. Now since the scsi layer in ll_rw_blk.c
is doing a fiddling and attaching the new buffer heads to already
existing requests it seems Im missing them out.
Ive solved the problem by adding a few lines of code very similar
to md request in ll_rw_block(). Hence I have created a hook up function on
to which I can hook myself to capture every single buffer head.
If there is a more elegant way of doing the same, please guide me.
Alternatively if the scsi layer is going to be modified, I would like to
know If such an interface would be possible in the future for me without
myself adding hook up functions.
Regards
Animesh Singh
& P.Basker
PS: Is there only u and me in the mailing list?
>
> Offhand I am not sure why you are getting this - mainly because I am not
> sure what you are actually viewing. I would tend to suspect that the
> logging code isn't always displaying something when a request is started,
> but that's just a guess.
>
> -Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
