From mboxrd@z Thu Jan 1 00:00:00 1970 From: mricon at kernel.org (Konstantin Ryabitsev) Date: Wed, 12 Oct 2016 09:05:54 -0400 Subject: RFC: don't cache objects larger than X In-Reply-To: References: <20161010140312.GB2142@gmail.com> Message-ID: <20161012130554.GA2200@gmail.com> On Wed, Oct 12, 2016 at 01:22:34PM +0200, Jason A. Donenfeld wrote: > I face this same problem, in fact. Unless somebody beats me to it, I'd > be interested in giving this a stab. > > One issue is that cache entries are currently "streamed" into the > cache files, as they're produced. It's not trivially possible to know > how big it's going to be beforehand. This means that the best we could > do would be to just immediately unlink it after creation and printing. > Would this be acceptable? Is there any way of keeping track of how much was written? It seems like it should be pretty simple to continuously check how much has been written to the cache and abort writing if the cache file grows larger than the configured maximum? Best, -- Konstantin Ryabitsev Linux Foundation Collab Projects Montr?al, Qu?bec -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: