Hi, snippet from File: libs/services/libblkdev/genstor.c Line 343 ret = read_bio_rpc_data(bio_rpc, 0, bio_rpc->size, (void*)((ulong_t)bio_rpc->data_buf + off));
Becaus of rpc debugging become a but cumbersome :) I would like to know, In case of write to disks, what is purpose of read_bio_rpc_data, I think reading buf which is being to be written to disk, so that we pass it to next layers? Thanks, Shiv On Wed, Aug 11, 2010 at 8:22 PM, Alfeiks Kaanoken <[email protected]>wrote: > > > >Hi, > Hi, > > > >Yes I did not fully turned off the bcahce but disabled it by directly > >calling devio_[read/write_block]_direct in dev_io.[ch] and bypass the > bchace > >and monitoring each call and analyzing data like inode bitmap and block > >bitmap before write and again re-read it in dev_io module only to verify > if > >read data is same as just written to disk but which is different. > I have a quick look around for dev_io.[c|h] I didn't find any problems, > but anyway I need to make a sense what are going on in your case. > > > >traces I doint have now, as I added some debug messages in ATA devices and > >will send you new traces soon. > Ok, I will wait for it. > > > >Thanks, > >Shivpratap > Thanks, > > > -- > Alfeiks Kaänoken, > Team Lead of the > Jari OS R&D Team. > http://jarios.org > Free open-source > microkernel-based > multiservice RTOS > _______________________________________________ > Jarios-dev mailing list > [email protected] > http://lists.jarios.org/cgi-bin/mailman/listinfo/jarios-dev >
_______________________________________________ Jarios-dev mailing list [email protected] http://lists.jarios.org/cgi-bin/mailman/listinfo/jarios-dev
