From: Shehbaz J. <she...@gm...> - 2013-04-21 11:31:48
|
Hi, I am trying to understand the example fuse implementation of fuse. I noticed that along with the hello.c file, there is another file hello_ll.c that describes the same operations mentioned in hello.c file. What is the use of hello_ll.c file? Does ll stand for low level? Currently hello.c file supports getattr, readattr, read, open functions. If I add new functions (write, mknod etc.) Do i need to add these functions in hello_ll.c file also? Thanks. -- Shehbaz Jaffer |
From: Nikolaus R. <Nik...@ra...> - 2013-04-21 19:39:07
|
Shehbaz Jaffer <she...@pu...> writes: > Hi, > > I am trying to understand the example fuse implementation of fuse. I > noticed that along with the hello.c file, there is another file hello_ll.c > that describes the same operations mentioned in hello.c file. > > What is the use of hello_ll.c file? Does ll stand for low level? Yes. hello.c is an example of implementing a file system with the high level API. hello_ll.c is an example for implementing a file system with the low-level api. > Currently hello.c file supports getattr, readattr, read, open functions. If > I add new functions (write, mknod etc.) Do i need to add these functions in > hello_ll.c file also? No, hello.c and hello_ll.c are independent programs. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C |