github/open-cas-linux
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Restore the explanation for NOMERGES flag

Browse Source 
The comment was remved in 1e5355eba1

Signed-off-by: Michal Mielewczyk <michal.mielewczyk@huawei.com>
This commit is contained in:
Michal Mielewczyk 2024-09-20 09:25:52 +02:00
parent ae2d14dfb2
commit a1629790af
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
configure.d/1_queue_limits.conf
View File

@ -49,6 +49,14 @@ apply() {
exp_q->limits.max_write_same_sectors = 0; exp_q->limits.max_write_same_sectors = 0;
}" }"
# A workaround for RHEL/CentOS 7.3 bug in kernel.
# Merging implementation on blk-mq does not respect virt boundary
# restriction and front merges bios with non-zero offsets.
# This leads to request with gaps between bios and in consequence
# triggers BUG_ON() in nvme driver or silently corrupts data.
# To prevent this, disable merging on cache queue if there are
# requirements regarding virt boundary (marking bios with REQ_NOMERGE
# does not solve this problem).
add_function " add_function "
static inline void cas_cache_set_no_merges_flag(struct request_queue *cache_q) static inline void cas_cache_set_no_merges_flag(struct request_queue *cache_q)
{ {