1 .TH llapi_pcc_attach 3 "2019 April 20" "Lustre User API"
3 llapi_pcc_attach, llapi_pcc_attach_fid, llapi_pcc_attach_fid_str \- attach a file into PCC
6 .B #include <lustre/lustreapi.h>
8 .BI "int llapi_pcc_attach(const char *" path ", __u32 " id ,
9 .BI " enum lu_pcc_type " type ");"
11 .BI "int llapi_pcc_attach_fid(const char *" mntpath ", const struct lu_fid *" fid ,
12 .BI " __u32 " id ", enum lu_pcc_type " type ");"
14 .BI "int llapi_pcc_attach_fid_str(const char *" mntpath ", const char *" fidstr ,
15 .BI " __u32 " id ", enum lu_pcc_type " type ");"
20 .BR llapi_pcc_attach() ,
21 .BR llapi_pcc_attach_fid() ,
23 .BR llapi_pcc_attach_fid_str()
24 tries to attach the file referenced by
29 into PCC backend. PCC provides a group of local caches and works in two modes:
30 RW-PCC enables a read-write cache on the local SSDs of a single client; RO-PCC
31 provides a read-only cache on the local SSDs of multiple clients. For RW-PCC,
34 is the archive ID of the copytool agent running on this client. By default,
35 RO-PCC attach ID is setting same with RW-PCC attach ID for a PCC backend if it
36 is also used as read-only caching. The attach mode is specified by
40 data structure, which contains the following values:
49 menas that the file is not cached on PCC.
59 return 0 on success or a negative errno value on failure.
63 Insufficient memory to complete operation.
66 Memory region is not properly mapped.
69 One or more invalid arguments are given.
72 PCC attach operation is not supported.