A few more spelling fixes.
This commit is contained in:
parent
8c35235c34
commit
f17721c364
@ -12,7 +12,7 @@ Data block, default AES-GCM mode
|
||||
1-4096 bytes encrypted data
|
||||
16 bytes GHASH
|
||||
|
||||
Data block, AES-SIV mode (used in reverse mode, or when explicitely enabled with `-init -aessiv`)
|
||||
Data block, AES-SIV mode (used in reverse mode, or when explicitly enabled with `-init -aessiv`)
|
||||
|
||||
16 bytes nonce
|
||||
16 bytes SIV
|
||||
|
@ -14,8 +14,8 @@ import (
|
||||
const (
|
||||
// Number of entries in the dirCache. Three entries work well for two
|
||||
// (probably also three) parallel tar extracts (hit rate around 92%).
|
||||
// Keen in sync with test_helpers.maxCacheFds !
|
||||
// TODO: How to share this constant without causing in import cycle?
|
||||
// Keep in sync with test_helpers.maxCacheFds !
|
||||
// TODO: How to share this constant without causing an import cycle?
|
||||
dirCacheSize = 3
|
||||
// Enable Lookup/Store/Clear debug messages
|
||||
enableDebugMessages = false
|
||||
@ -52,7 +52,7 @@ type dirCacheStruct struct {
|
||||
entries [dirCacheSize]dirCacheEntryStruct
|
||||
// Where to store the next entry (index into entries)
|
||||
nextIndex int
|
||||
// On the first Lookup(), the expire thread is stared, and this flag is set
|
||||
// On the first Lookup(), the expire thread is started, and this flag is set
|
||||
// to true.
|
||||
expireThreadRunning bool
|
||||
// Hit rate stats. Evaluated and reset by the expire thread.
|
||||
|
@ -123,8 +123,8 @@ func UnmountPanic(dir string) {
|
||||
}
|
||||
|
||||
// gocryptfs may hold up to maxCacheFds open for caching
|
||||
// Keen in sync with fusefrontend.dirCacheSize
|
||||
// TODO: How to share this constant without causing in import cycle?!
|
||||
// Keep in sync with fusefrontend.dirCacheSize
|
||||
// TODO: How to share this constant without causing an import cycle?!
|
||||
const maxCacheFds = 3
|
||||
|
||||
// UnmountErr tries to unmount "dir", retrying 10 times, and returns the
|
||||
|
Loading…
Reference in New Issue
Block a user