|author||Seebs <email@example.com>||2018-01-16 20:06:30 -0600|
|committer||Seebs <firstname.lastname@example.org>||2018-01-16 20:06:30 -0600|
FASTOP is logically fine as long as there's no errors, but if there could be errors, we lose error detection. Responding instantly with a trivial ACK for FASTOP messages slightly reduces performance but improves reliability and seems to work better. Signed-off-by: Seebs <email@example.com>
Diffstat (limited to 'ChangeLog.txt')
1 files changed, 2 insertions, 0 deletions
diff --git a/ChangeLog.txt b/ChangeLog.txt
index 4f58922..d334dec 100644
@@ -9,6 +9,8 @@
* (seebs) add wrapper for statvfs (based on patch from
* (seebs) Call this 1.9.0.
+ * (seebs) Experimental-ish: Require a response even for FASTOP
+ just to confirm delivery of message/server availability.
* (seebs) handle the pathological case of LINKAT with