Skip to content

Tested with fsstress #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 9 commits into
base: master
Choose a base branch
from
Open

Tested with fsstress #29

Changes from 2 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
683fabc
Merge pull request #2 from utsaslab/master
KrishnanGosakan Jul 25, 2020
f4023af
Update README.md
KrishnanGosakan Jul 25, 2020
3a6eb38
Merge pull request #3 from utsaslab/master
KrishnanGosakan Aug 2, 2020
14c333a
added fsstress related files in splitfs repo
KrishnanGosakan Aug 2, 2020
4bc105b
changes due to fsstress licence
KrishnanGosakan Aug 15, 2020
f850b66
removed fsstress directory due to licence issue
KrishnanGosakan Aug 15, 2020
5568440
fsstress readme changes
KrishnanGosakan Aug 19, 2020
7010da6
readme file added endline
KrishnanGosakan Aug 19, 2020
7786f59
removed unwanted file
KrishnanGosakan Aug 20, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@ The kernel patch for the implementation of relink() system call for linux v4.13
## Limitations
SplitFS is under active development.
1. The current implementation of SplitFS handles the following system calls: `open, openat, close, read, pread64, write, pwrite64, fsync, unlink, ftruncate, fallocate, stat, fstat, lstat, dup, dup2, execve and clone`. The rest of the calls are passed through to the kernel.
2. The current implementation of SplitFS works correctly for the following applictions: `LevelDB running YCSB, SQLite running TPCC, tar, git, rsync`. This limitation is purely due to the state of the implementation, and we aim to increase the coverage of applications by supporting more system calls in the future.
2. The current implementation of SplitFS works correctly for the following applictions: `LevelDB running YCSB, SQLite running TPCC, tar, git, rsync, fsstress`. This limitation is purely due to the state of the implementation, and we aim to increase the coverage of applications by supporting more system calls in the future.

## Applications currently supported
1. LevelDB (with YCSB)
Expand All @@ -120,6 +120,7 @@ SplitFS is under active development.
3. git
4. tar
5. rsync
6. fsstress

## Testing
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should come under Testing category rather than in applications supported

[PJD POSIX Test Suite](https://www.tuxera.com/community/posix-test-suite/) that tests primarily the metadata operations was run on SplitFS successfully. SplitFS passes all tests.
Expand Down