KernReadFileAtCache: Difference between revisions

Revision as of 21:50, 9 June 2017

This seems to do the same as KernReadAtFile, but reads from the cache and returns the corresponding pages of the cache data structure.

APIRET APIENTRY KernReadFileAtCache(KEEhfile khfd,KEECachePages** ptr, QWORD off, ULONG nbytes, PULONG nread);

khfd: SFT pointer
ptr: Pointer to a variable the receives the cache data structure for the specified data blocks.
off: 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.

Yet another JFS hack. Meanwhile I understand why IBM is reluctant to provide JFS support for Warp 4.

@@ 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==
 APIRET APIENTRY KernReadFileAtCache(KEEhfile khfd,KEECachePages** ptr, QWORD off, ULONG nbytes, PULONG nread);
-==Description==
-This seems to do the same as KernReadAtFile, but reads from the cache and returns the corresponding pages of the cache data structure.
 ==Parameters==
-khfd
+; khfd :     SFT pointer
-     SFT pointer
+; ptr :     Pointer to a variable the receives the cache data structure for the specified data blocks.
-ptr
+; off :     Offset in file to start reading
-     Pointer to a variable the receives the cache data structure for the specified data blocks.
+; nbytes :     Number of bytes to read
-off
+; nread :     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==
 Yet another JFS hack. Meanwhile I understand why IBM is reluctant to provide JFS support for Warp 4.
-[[Category:Kern]]
+[[Category:KEE]]