FMappedRegionPakProxy Class Reference

Inheritance diagram for FMappedRegionPakProxy:

Public Member Functions
	FMappedRegionPakProxy (TSharedPtr< IMappedFileHandle > InParent, TUniquePtr< IMappedFileRegion > InLowerLevel, const FString &InDebugFilename, size_t InDebugOffsetIntoFile)
virtual void	PreloadHint (int64 PreloadOffset=0, int64 BytesToPreload=MAX_int64) override
Public Member Functions inherited from IMappedFileRegion
	IMappedFileRegion (const uint8 *InMappedPtr, size_t InMappedSize, const FString &InDebugFilename, size_t InDebugOffsetRelativeToFile)
virtual	~IMappedFileRegion ()
const uint8 *	GetMappedPtr ()
int64	GetMappedSize ()
virtual void	Flush (int64 FlushOffset=0, int64 BytesToFlush=MAX_int64)
	IMappedFileRegion (const IMappedFileRegion &)=delete
IMappedFileRegion &	operator= (const IMappedFileRegion &)=delete

Constructor & Destructor Documentation

FMappedRegionPakProxy()

FMappedRegionPakProxy::FMappedRegionPakProxy ( TSharedPtr< IMappedFileHandle >  InParent, TUniquePtr< IMappedFileRegion >  InLowerLevel, const FString &  InDebugFilename, size_t  InDebugOffsetIntoFile  )

inline

Member Function Documentation

PreloadHint()

virtual void FMappedRegionPakProxy::PreloadHint ( int64  PreloadOffset = 0, int64  BytesToPreload = MAX_int64  )

inlineoverridevirtual

Synchronously preload part or all of the mapped region. Typically this is done by reading a byte from each CPU page. This is only a hint, some platforms might ignore it. There are not guarantees how long this data will stay in memory.

Parameters

PreloadOffset	Offset into this region to preload
BytesToPreload	number of bytes to preload. This is clamped to the size of the mapped region

Reimplemented from IMappedFileRegion.

---

The documentation for this class was generated from the following file:

• Engine/Source/Runtime/PakFile/Private/IPlatformFilePak.cpp