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.

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

Jump to bottom

Acquire stat and hashes in kext to move burden to caller #11

Open
droe opened this issue Jun 16, 2018 · 2 comments
Open

Acquire stat and hashes in kext to move burden to caller #11

droe opened this issue Jun 16, 2018 · 2 comments
Labels
type:feature request for additional functionality type:kext

Comments

@droe
Copy link
Owner

droe commented Jun 16, 2018 •
edited

Consider acquiring stat and hashes in-kernel in order to move burden to the task calling exec. This should reduce the amount of time the main thread spends acquiring data the event loop. Requires a separate or shared cache in the kext. Needs extra care when dealing with network file systems, perhaps by delegating acquisition to userspace if path is located on a network file system.
@droe droe added the type:feature request for additional functionality label Jun 16, 2018
@droe droe added the status:blocked depends on other unresolved issue, github or external label Jul 23, 2018
@droe
Copy link
Owner Author

droe commented Jul 23, 2018

Blocked by #6

@droe droe changed the title [kext] Consider acquiring stat and hashes in kext Acquire stat and hashes in kext to move burden to caller Aug 1, 2018
@droe droe added the type:kext label Aug 1, 2018
@droe droe removed the status:blocked depends on other unresolved issue, github or external label Sep 21, 2018
@droe
Copy link
Owner Author

droe commented Sep 21, 2018

Unblock, as #6 is resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:feature request for additional functionality type:kext
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@droe