Skip to content
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.

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

Implement SplitFS using system-call interception rather than library calls #32

Open
vijay03 opened this issue Jul 31, 2020 · 8 comments

Comments

@vijay03
Copy link
Member

vijay03 commented Jul 31, 2020

Use the system-call intercept library: https://github.com/pmem/syscall_intercept in SplitFS instead of intercepting glibc calls. This will make SplitFS more portable and hopefully more robust (different glibc variants will have the same system call implementation).

@ishank-arora
Copy link

Is it possible for me to work on this?

@OmSaran
Copy link
Contributor

OmSaran commented Jan 20, 2021

@vijay03 @rohankadekodi
I have been working on this.
Current status: POSIX (pjd) test suite integrated and passing successfully in POSIX mode SplitFS.

@vijay03
Copy link
Member Author

vijay03 commented Jan 20, 2021

Thats great! Can we get a pull request?

@OmSaran
Copy link
Contributor

OmSaran commented Jan 20, 2021

@vijay03 I have created a draft pull request. #47
Draft because:

  1. There are some unwanted files (Quill related) that can be removed (In progress)
  2. I wanted to integrate Sync and Strict mode also in this PR itself.

Looking to get above 2 done by 25th Jan.

I was thinking of converting to full pull request once above 2 are complete. Would that be ok?

@vijay03
Copy link
Member Author

vijay03 commented Jan 20, 2021

That would be great! Let us know when @rohankadekodi and I can review it.

@rohankadekodi
Copy link
Collaborator

rohankadekodi commented Jan 21, 2021 via email

@OmSaran
Copy link
Contributor

OmSaran commented Jan 24, 2021

@vijay03 @rohankadekodi
sync and strict integration is also complete and ready for review. I have included some details of the PR in the PR description. #47

@rohankadekodi
Copy link
Collaborator

rohankadekodi commented Jan 25, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants