Date: Tue, 03 May 2011 13:48:26 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: freebsd-fs@FreeBSD.org, Alexander Motin <mav@FreeBSD.org> Subject: Re: TRIM clustering Message-ID: <20110503134826.712070yt2urhxp8g@webmail.leidinger.net> In-Reply-To: <20110501133752.GC3245@garage.freebsd.pl> References: <4DBBB20A.5050102@FreeBSD.org> <20110430072831.GA65598@icarus.home.lan> <20110501000656.00007ea1@unknown> <20110501133752.GC3245@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Pawel Jakub Dawidek <pjd@FreeBSD.org> (from Sun, 1 May 2011 15:37:52 +0200): > On Sun, May 01, 2011 at 12:06:56AM +0200, Alexander Leidinger wrote: >> On Sat, 30 Apr 2011 00:28:31 -0700 Jeremy Chadwick >> <freebsd@jdc.parodius.com> wrote: >> >> > On Sat, Apr 30, 2011 at 09:54:02AM +0300, Alexander Motin wrote: >> >> > Other notes: TRIM needs to be supported on swap as well, and in my >> > opinion this is just as important as it being in UFS. I'm not sure >> > how one would implement that. >> >> This brings up the question if a ZFS cache (where the contents do not >> survive a reboot) is completely TRIMmed before used (and normally >> trimmed during use)... > > It is not trimmed at all. This does not sound like the optimal solution... is there a way to know the first access after boot/attach to a cache device? If yes, would it be possible to TRIM the complete provider (except for some static data which needs to be there) from this place? This would not solve the not TRIMmed during use part, put at least a reboot/reattach could provide a sane state. Bye, Alexander. -- BOFH excuse #189: SCSI's too wide http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110503134826.712070yt2urhxp8g>