diff options
| author | Jakob Unterwurzacher | 2021-08-30 20:00:00 +0200 |
|---|---|---|
| committer | Jakob Unterwurzacher | 2021-08-30 20:00:00 +0200 |
| commit | c505e73a13d8e2083b53c5c1af1f937b46665abd (patch) | |
| tree | 92cb767989d1957ad8c99b4b8d10ff8f10d8cbd6 | |
| parent | 4e3b7702aff72283fb9a999e6568bdfd41581fd5 (diff) | |
README: explain where -xchacha makes sense
| -rw-r--r-- | README.md | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -203,6 +203,7 @@ v2.2, IN PROGRESS Gives [better performance on embedded CPUs](https://gist.github.com/rfjakob/b28383f4c84263ac7c5388ccc262e38b) ([#452](https://github.com/rfjakob/gocryptfs/issues/452)) * New feature flag! You need gocryptfs v2.2 or higher to mount a filesystem that uses this flag. + * Test with `gocryptfs -speed` what is fastest for your CPU, or read [here](https://github.com/rfjakob/gocryptfs/issues/452#issuecomment-908559414) * `-serialize_reads`: get rid of delay logic by taking advantage of the kernel flag `FUSE_CAP_ASYNC_READ` ([go-fuse commit](https://github.com/hanwen/go-fuse/commit/15a8bb029a4e1a51e10043c370970596b1fbb737), |