From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kai Krakow Subject: Re: what happened to the nifty ioprio cache hinting stuff? Date: Sat, 6 May 2017 12:37:02 +0200 Message-ID: <20170506123702.2e8e66e3@jupiter.sol.kaishome.de> References: <877f1zil5d.fsf@esperi.org.uk> <20170502201559.5cd65131@jupiter.sol.kaishome.de> <874lwzasaq.fsf@esperi.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from [195.159.176.226] ([195.159.176.226]:57010 "EHLO blaine.gmane.org" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1751824AbdEFKkM (ORCPT ); Sat, 6 May 2017 06:40:12 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1d6x87-0007tx-PX for linux-bcache@vger.kernel.org; Sat, 06 May 2017 12:40:03 +0200 Sender: linux-bcache-owner@vger.kernel.org List-Id: linux-bcache@vger.kernel.org To: linux-bcache@vger.kernel.org Am Fri, 05 May 2017 22:48:45 +0100 schrieb Nix : > On 2 May 2017, Kai Krakow said: > > > Am Tue, 02 May 2017 11:54:38 +0100 > > schrieb Nix : > > > >> I found the ioprio cache hinting quite exciting (I know, I'm > >> weird): it won't help with writeback or e.g. NFS, but it will > >> certainly let me do things like run backups without wearing my SSD > >> out. > > > > I'm certainly waiting for the patches to be upstreamed. Meanwhile, I > > stopped the hassle of applying the patches and just resorted to > > putting my backups partition into "write-around" mode. It still > > gets big improvements in performance and is nice to wear leveling. > > I'm running in writearound mode regardless, since my bcache is atop an > md array, and that array is journalled on the same SSD (for powerfail > reliability and because in write-back mode it greatly speeds up > writes), and I don't want to burn the SSD out *that* badly. It still > speeds things up hugely :) > > >> This was in ewheeler's for-4.10-block-bcache-updates branch, but it > >> didn't get into 4.10 or 4.11, even while other commits on the same > >> branch did :( is it dead? (I mean, it still seems to *apply* to > >> 4.11...) > > > > Last time I looked at bitbucket (the only place I found it) to pull > > the patches via http, it was horribly slow and even complained that > > the repository is too big to be browsed or generate patch sets. > > > > Would it be possible to mirror it somewhere else? Bitbucket is > > really slow for me, direct git-clone didn't even work. > > > > I was just trying to pull the branch and rebase it ontop of current > > kernels myself because I couldn't apply these patches. But I > > eventually gave up due to bitbuckets superior *cough* > > performance... :-( > > It is much faster to take an existing kernel working tree and do a > > git remote add ewheeler https://bitbucket.org/ewheelerinc/linux.git > git remote update ewheeler > > since this only needs to get a few hundred KiB of objects. Yes, that worked... While I've been at that, I also rebased the bfq patches to get the latest bfq version for ck-sources. Although it took about a minute to connect to bitbucket - but pulling the data itself was fast then, matter of eye blinks. -- Regards, Kai Replies to list-only preferred.