KernReadFileAtCache: Difference between revisions
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
==Parameters== | ==Parameters== | ||
; khfd : SFT pointer | ; khfd (KEEhfile) - input : SFT pointer | ||
; ptr : Pointer to a variable the receives the cache data structure for the specified data blocks. | ; ptr (KEECachePages**) - input: Pointer to a variable the receives the cache data structure for the specified data blocks. | ||
; off : Offset in file to start reading | ; off ([[QWORD]]) - input: Offset in file to start reading | ||
; nbytes : Number of bytes to read | ; nbytes ([[ULONG]]) - input: Number of bytes to read | ||
; nread : Pointer to an ULONG to receive the number of bytes actually read. | ; nread (PULONG) - input: Pointer to an ULONG to receive the number of bytes actually read. | ||
==Comments== | ==Comments== | ||
Revision as of 03:36, 28 May 2025
This seems to do the same as KernReadAtFile, but reads from the cache and returns the corresponding pages of the cache data structure.
Synopsis
APIRET APIENTRY KernReadFileAtCache(KEEhfile khfd,KEECachePages** ptr, QWORD off, ULONG nbytes, PULONG nread);
Parameters
- khfd (KEEhfile) - input
- SFT pointer
- ptr (KEECachePages**) - input
- Pointer to a variable the receives the cache data structure for the specified data blocks.
- off (QWORD) - input
- Offset in file to start reading
- nbytes (ULONG) - input
- Number of bytes to read
- nread (PULONG) - input
- Pointer to an ULONG to receive the number of bytes actually read.
Comments
Yet another JFS hack. Meanwhile I understand why IBM is reluctant to provide JFS support for Warp 4.