mittal wrote:
> request structure in kernel 2.6.28.7
>
> /* no. of sectors left to submit in the current segment */
> unsigned int current_nr_sectors;
>
> /* no. of sectors left to complete in the current segment */
> unsigned int hard_cur_sectors;
>
hi all
from many days i was posting many problems on mailing list related to
request structure processing confusion
and was getting null replies
and i know many like me are confused over this ...
so to help all those like me read this link ---best link i have read solves
all confusions ...
http
request structure in kernel 2.6.28.7
/* no. of sectors left to submit in the current segment */
unsigned int current_nr_sectors;
/* no. of sectors left to complete in the current segment */
unsigned int hard_cur_sectors;
Are these two fields different in it ...they seem
-- Forwarded message --
From: nidhi mittal
Date: Wed, Feb 18, 2009 at 4:37 PM
Subject: block device driver request structure --- doubt
To: Kernelnewbies , Sandeep Nashikkar <
sandeep11j...@gmail.com>
hi all
i was practising writing block device driver from linux device
hi all
i was practising writing block device driver from linux device driver 3rd
edition
but was confused
as
it gives two implementation to transfer data from device
1.without using bios
2.using bios
in ist implementation cut short version of book code is -
while ((req = elv_next_reque
Hi,
Le Thu, 15 Nov 2007 17:57:41 +0530,
"Adil Mujeeb" <[EMAIL PROTECTED]> a écrit :
> I am not able to understand the meaning / usage of following members:
A "struct request" potentially aggregates several "struct bio", which
are stored in a linked-list available through the request->bio field.
Hi,
I was going through the request descriptor data structure (strcut request)
in the Oreilly book.
I am not able to understand the meaning / usage of following members:
unsigned long nr_sectors : Number of sectors yet to be transferred in the
whole request
unsigned int current_nr_secto
