Development and Implementation of a File System for Gannet Virtual ...

More documents

Recommendations

Info

APPENDICES 61
A. Requirement Specification Functional Requirement The file system must operate in user space without rely on kernel. The file system must be able to create new file. The file system must be able to read a file. The file system must be able to write a file. The file system must be able to remove a file. The file system must be able to create new directory. The file system must be able to remove a directory. The file system should support random access on a file. The file system should support streaming feature. The file system should be able to perform copy operation. The file system should be able to perform move operation. Non-Functional Requirement The file system’s interface must comply to POSIX standard. The file system must be developed and implemented using C/C++ programming language. 62
Page 1 and 2:
Development and Implementation of a
Page 3 and 4:
Abstract This project is addressed
Page 5 and 6:
4.3 Integration to Gannet Virtual M
Page 7 and 8:
communication architecture (Kogel,
Page 9 and 10:
Survey 2.1 Gannet System Overview G
Page 11 and 12:
Figure 2.2 Service-based SoC Node (
Page 13 and 14:
Service 2 Gannet Functionality Serv
Page 15 and 16: On the other hand, if large allocat
Page 17 and 18: Indexed allocation has different ap
Page 19 and 20: GannetFS will follow the RAM file s
Page 21 and 22: explained above are not suitable fo
Page 23 and 24: is quite small. Furthermore, the si
Page 25 and 26: Design 3.1 Requirement This section
Page 27 and 28: GannetFS file system is different w
Page 29 and 30: using this mechanism, the system al
Page 31 and 32: 3.2.2 File Allocation As discussed
Page 33 and 34: GannetFS file system treats these t
Page 35 and 36: 3.2.2.2 Directory Entry Data Struct
Page 37 and 38: Managing directory and path names i
Page 39 and 40: File Descriptor . . . . Stat Struct
Page 41 and 42: (Lewine 1991). Since POSIX also pro
Page 43 and 44: fields will remain the same. Howeve
Page 45 and 46: directory entry. Hence, there is no
Page 47 and 48: Uid 256 Uid 64 Uid Size 320 drwxrwx
Page 49 and 50: ack onto the stack to be reused and
Page 51 and 52: According to illustration on Figure
Page 53 and 54: Testing and Evaluation 5.1 Testing
Page 55 and 56: MAX_NAME_PATH or fewer characters.
Page 57 and 58: 5.2 Evaluation Unlike testing which
Page 59 and 60: 5.2.2 Read Only Memory Evaluation I
Page 61 and 62: Operation Cycles Creat 6722 Open (F
Page 63 and 64: Conclusion This project was underta
Page 65: Silberschats, A., Galvin, P.B., Gag
Page 69 and 70: nbyte : Maximum number of bytes to
Page 71 and 72: 10. readdir() : Reads a directory.
Page 73 and 74: C. Testing TestCase00 Creates, writ
Page 75 and 76: TestCase04 This test case creates 1
Page 77: TestCase10 Writes data to and reads
show all

Development and Implementation of a File System for Gannet Virtual ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?