Hi
In regular read dispatch, I read myself by considering
ioStack->Parameters.Read.Length as buffer length. I set file offset, irp
IoStatus and complete the IRP. But I am not receiving further read
eventhough the file is bigger.
Do I need to consider using UserIosb->Information as buffer length to read
data?
Thanks
Ramaraj
No, ioStack->Parameters.Read.Length is correct. Drivers must not
touch ->UserIosb, it is only to transfer information from Ntxxx IO
calls to IopCompleteRequest.
Why you’re not receiving “further read” is not a driver’s problem.
Max
----- Original Message -----
From: “Ramaraj Pandian”
To: “File Systems Developers”
Sent: Thursday, May 22, 2003 4:21 AM
Subject: [ntfsd] read length
> Hi
>
> In regular read dispatch, I read myself by considering
> ioStack->Parameters.Read.Length as buffer length. I set file offset,
irp
> IoStatus and complete the IRP. But I am not receiving further read
> eventhough the file is bigger.
>
> Do I need to consider using UserIosb->Information as buffer length
to read
> data?
>
> Thanks
> Ramaraj
>
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
Thanks Max.
I am missing some obvious thing.
If read happens on non protected file, same behaviour but it gets all data
with one shot eventhough read length is 512 bytes.
I just do “type file” from command prompt.
-Ramaraj
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
Sent: Wednesday, May 21, 2003 7:14 PM
To: File Systems Developers
Subject: [ntfsd] Re: read length
No, ioStack->Parameters.Read.Length is correct. Drivers must not
touch ->UserIosb, it is only to transfer information from Ntxxx IO
calls to IopCompleteRequest.
Why you’re not receiving “further read” is not a driver’s problem.
Max
----- Original Message -----
From: “Ramaraj Pandian”
To: “File Systems Developers”
Sent: Thursday, May 22, 2003 4:21 AM
Subject: [ntfsd] read length
> Hi
>
> In regular read dispatch, I read myself by considering
> ioStack->Parameters.Read.Length as buffer length. I set file offset,
irp
> IoStatus and complete the IRP. But I am not receiving further read
> eventhough the file is bigger.
>
> Do I need to consider using UserIosb->Information as buffer length
to read
> data?
>
> Thanks
> Ramaraj
>
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to ntfsd as: xxxxx@vormetric.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
are u missing the fastio reads?
Ampsi
----- Original Message -----
From: “Ramaraj Pandian”
To: “File Systems Developers”
Sent: Thursday, May 22, 2003 10:32
Subject: [ntfsd] Re: read length
Thanks Max.
I am missing some obvious thing.
If read happens on non protected file, same behaviour but it gets all data
with one shot eventhough read length is 512 bytes.
I just do “type file” from command prompt.
-Ramaraj
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
Sent: Wednesday, May 21, 2003 7:14 PM
To: File Systems Developers
Subject: [ntfsd] Re: read length
No, ioStack->Parameters.Read.Length is correct. Drivers must not
touch ->UserIosb, it is only to transfer information from Ntxxx IO
calls to IopCompleteRequest.
Why you’re not receiving “further read” is not a driver’s problem.
Max
----- Original Message -----
From: “Ramaraj Pandian”
To: “File Systems Developers”
Sent: Thursday, May 22, 2003 4:21 AM
Subject: [ntfsd] read length
> Hi
>
> In regular read dispatch, I read myself by considering
> ioStack->Parameters.Read.Length as buffer length. I set file offset,
irp
> IoStatus and complete the IRP. But I am not receiving further read
> eventhough the file is bigger.
>
> Do I need to consider using UserIosb->Information as buffer length
to read
> data?
>
> Thanks
> Ramaraj
>
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to ntfsd as: xxxxx@vormetric.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to ntfsd as: xxxxx@pmail.ntu.edu.sg
To unsubscribe send a blank email to xxxxx@lists.osr.com
“Ramaraj Pandian” wrote in message
news:xxxxx@ntfsd…
>
> Thanks Max.
>
> I am missing some obvious thing.
> If read happens on non protected file, same behaviour but it gets all data
> with one shot eventhough read length is 512 bytes.
Do you mean that you saw read request from application for 512 bytes only,
but application received more than 512 byte of data?
Read request from application could be satisfied via FastIO path without any
IRP involved.
>
> I just do “type file” from command prompt.
Thanks Alexei and Ampsi.
Yes that may be case.
-Ramaraj
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Alexei Jelvis
Sent: Wednesday, May 21, 2003 8:02 PM
To: File Systems Developers
Subject: [ntfsd] Re: read length
“Ramaraj Pandian” wrote in message
news:xxxxx@ntfsd…
>
> Thanks Max.
>
> I am missing some obvious thing.
> If read happens on non protected file, same behaviour but it gets all data
> with one shot eventhough read length is 512 bytes.
Do you mean that you saw read request from application for 512 bytes only,
but application received more than 512 byte of data?
Read request from application could be satisfied via FastIO path without any
IRP involved.
>
> I just do “type file” from command prompt.
—
You are currently subscribed to ntfsd as: xxxxx@vormetric.com
To unsubscribe send a blank email to xxxxx@lists.osr.com