KernReadFileAtCache: Difference between revisions
m Ak120 moved page OS2 API:KEE:KernReadFileAtCache to KernReadFileAtCache |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This seems to do the same as KernReadAtFile, but reads from the cache and returns the corresponding pages of the cache data structure. | |||
==Synopsis== | ==Synopsis== | ||
APIRET APIENTRY KernReadFileAtCache(KEEhfile khfd,KEECachePages** ptr, QWORD off, ULONG nbytes, PULONG nread); | APIRET APIENTRY KernReadFileAtCache(KEEhfile khfd,KEECachePages** ptr, QWORD off, ULONG nbytes, PULONG nread); | ||
==Parameters== | ==Parameters== | ||
khfd | ; ''khfd'' (KEEhfile) - input : SFT pointer | ||
SFT pointer | ; ''ptr'' (KEECachePages**) - input: Pointer to a variable the receives the cache data structure for the specified data blocks. | ||
ptr | ; ''off'' ([[QWORD]]) - input: Offset in file to start reading | ||
Pointer to a variable the receives the cache data structure for the specified data blocks. | ; ''nbytes'' ([[ULONG]]) - input: Number of bytes to read | ||
off | ; ''nread'' (PULONG) - input: Pointer to an ULONG to receive the number of bytes actually read. | ||
Offset in file to start reading | |||
nbytes | |||
Number of bytes to read | |||
nread | |||
Pointer to an ULONG to receive the number of bytes actually read. | |||
==Comments== | ==Comments== | ||
Yet another JFS hack. Meanwhile I understand why IBM is reluctant to provide JFS support for Warp 4. | Yet another JFS hack. Meanwhile I understand why IBM is reluctant to provide JFS support for Warp 4. | ||
[[Category:KEE]] | |||
[[Category: | |||
Latest revision as of 03:38, 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.