Date: Tue, 08 Jan 2019 03:36:42 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 234705] zpool initialize does not BIO_DELETE Message-ID: <bug-234705-3630-nx4AnnTB4f@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234705-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-234705-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=3D234705 Warner Losh <imp@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |imp@FreeBSD.org --- Comment #2 from Warner Losh <imp@FreeBSD.org> --- These days, BIO_DELETE is almost always a win. Writing zeros is a big lose often (though if the lower-layers implement a special WRITE ZEROS command, there might be some cases where that's useful: we currently do not). I doubt BOTH are ever anything but extra work. I would argue, however, that we shou= ld think carefully here. The difference between DSM Deallocate and WRITE ZEROS= + Deallocate flag (for those nvme drives that support it) is very small (trim= med blocks can return a variety of things depending: 0, ff or last written data= )... --=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-234705-3630-nx4AnnTB4f>