Date: Tue, 19 Feb 2019 10:30:24 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 209571] NVMe performing poorly. TRIM requests stall I/O activity Message-ID: <bug-209571-3630-tG48MYw9wL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209571-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-209571-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209571 --- Comment #13 from Borja Marcos <borjam@sarenet.es> --- (In reply to Peter Eriksson from comment #12) But that would suggest a firmware problem? In my experience with NVMEs the situation improved a lot with a firmware update. Although of course the lac= k of trmi collapse is a problem. I still think that maybe discarding TRIM operations in serious congestion situations is a lesser evil. After all, what are people doing when facing t= his issue? Disabling TRIMs. It's better to do some TRIMs than none at all.=20 Certainly you cannot discard read/write operations like you would discard packets on a network in order to enforce a bandwidth limit. Buffering them doesn't help either when applications need to commit data to storage. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209571-3630-tG48MYw9wL>