Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
S
slash
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
uplex-varnish
slash
Commits
9b1c40ad
Unverified
Commit
9b1c40ad
authored
May 22, 2024
by
Nils Goroll
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document a known short read issue
Ref #65
parent
ba32426c
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
20 additions
and
0 deletions
+20
-0
vmod_slash.man.rst
src/vmod_slash.man.rst
+10
-0
vmod_slash.vcc
src/vmod_slash.vcc
+10
-0
No files found.
src/vmod_slash.man.rst
View file @
9b1c40ad
...
...
@@ -1319,6 +1319,16 @@ get them implemented.
FELLOW KNOWN ISSUES
===================
* With `fellow` storage on XFS, spurious read errors - most likely
short reads - have been observed. While short reads are technically
legal to happen, handling them would complicate the `fellow` code
substantially, so a fix is currently not planned. If you require a
fix, please support the project and let us know, see _CONTRIBUTING_
in `README.rst`_ for details.
For best performance, it is recommended to use `fellow` storage on a
raw device.
* On Linux with ``io_uring``, by default, `fellow` registers all of
the memory cache as buffers using
:ref:`io_uring_register_buffers(3)` to achieve optimal performance
...
...
src/vmod_slash.vcc
View file @
9b1c40ad
...
...
@@ -1235,6 +1235,16 @@ get them implemented.
FELLOW KNOWN ISSUES
===================
* With `fellow` storage on XFS, spurious read errors - most likely
short reads - have been observed. While short reads are technically
legal to happen, handling them would complicate the `fellow` code
substantially, so a fix is currently not planned. If you require a
fix, please support the project and let us know, see _CONTRIBUTING_
in `README.rst`_ for details.
For best performance, it is recommended to use `fellow` storage on a
raw device.
* On Linux with ``io_uring``, by default, `fellow` registers all of
the memory cache as buffers using
:ref:`io_uring_register_buffers(3)` to achieve optimal performance
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment