本文整理汇总了Golang中github.com/jacobsa/fuse/fuseops.OpenFileOp.KeepPageCache方法的典型用法代码示例。如果您正苦于以下问题：Golang OpenFileOp.KeepPageCache方法的具体用法？Golang OpenFileOp.KeepPageCache怎么用？Golang OpenFileOp.KeepPageCache使用的例子？那么恭喜您, 这里精选的方法代码示例或许可以为您提供帮助。您也可以进一步了解该方法所在类github.com/jacobsa/fuse/fuseops.OpenFileOp的用法示例。
在下文中一共展示了OpenFileOp.KeepPageCache方法的4个代码示例，这些例子默认根据受欢迎程度排序。您可以为喜欢或者感觉有用的代码点赞，您的评价将有助于系统推荐出更棒的Golang代码示例。
示例1: OpenFile
func (fs *cachingFS) OpenFile(
ctx context.Context,
op *fuseops.OpenFileOp) (err error) {
fs.mu.Lock()
defer fs.mu.Unlock()
op.KeepPageCache = fs.keepPageCache
return
}示例2: OpenFile
// OpenFile opens a File, ie. indicates operations are to be done on this file.
//
// Required for fuse.FileSystem.
func (k *KodingNetworkFS) OpenFile(ctx context.Context, op *fuseops.OpenFileOp) error {
file, err := k.getFile(ctx, op.Inode)
if err != nil {
return err
}
file.Open()
handleID := k.setEntryByHandle(file)
op.Handle = handleID
// KeepPageCache tells Kernel to cache this file contents or not. Say an user
// opens a file on their local and then changes that same file on the VM, by
// setting this to be false, the user can close and open the file to see the
// changes. See https://goo.gl/vjhjFY.
op.KeepPageCache = false
return nil
}示例3: OpenFile
func (fs *Goofys) OpenFile(
ctx context.Context,
op *fuseops.OpenFileOp) (err error) {
fs.mu.Lock()
in := fs.getInodeOrDie(op.Inode)
fs.mu.Unlock()
fh := in.OpenFile(fs)
fs.mu.Lock()
defer fs.mu.Unlock()
handleID := fs.nextHandleID
fs.nextHandleID++
fs.fileHandles[handleID] = fh
op.Handle = handleID
op.KeepPageCache = true
return
}示例4: OpenFile
// LOCKS_EXCLUDED(fs.mu)
func (fs *fileSystem) OpenFile(
ctx context.Context,
op *fuseops.OpenFileOp) (err error) {
fs.mu.Lock()
defer fs.mu.Unlock()
// Find the inode.
in := fs.inodes[op.Inode].(*inode.FileInode)
// Allocate a handle.
handleID := fs.nextHandleID
fs.nextHandleID++
fs.handles[handleID] = handle.NewFileHandle(in, fs.bucket)
op.Handle = handleID
// When we observe object generations that we didn't create, we assign them
// new inode IDs. So for a given inode, all modifications go through the
// kernel. Therefore it's safe to tell the kernel to keep the page cache from
// open to open for a given inode.
op.KeepPageCache = true
return
}