public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-bcache@vger.kernel.org, Kai Krakow <kai@kaishome.de>
Subject: Re: what happened to the nifty ioprio cache hinting stuff?
Date: Fri, 05 May 2017 22:41:18 +0100	[thread overview]
Message-ID: <878tmbasn5.fsf@esperi.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.11.1705021726500.5014@mail.ewheeler.net> (Eric Wheeler's message of "Tue, 2 May 2017 17:26:55 +0000 (UTC)")

On 2 May 2017, Eric Wheeler outgrape:

> Hi Jens,
>
> It looks like there are still people interested (excited, even!) in the 
> sysfs entries for ioprio cache hinting in bcache.  

As an aside, I expect to use it for all sorts of things (like backups:
bup likes to reread all data sometimes, and I don't want to blow the
bcache when it does), but in particular I plan to use it for things I
know will be using large volumes of data for the last time before
destruction -- things like manual and automated 'git gc', where I know
that preserving the old packfiles in the bcache is a total waste of time
and where the packfiles being read in only to be deleted may be very
large.

(I'm running in writearound mode, so the lack of useful ioprio for
writeback is not a problem for me, and I can cope with the lack of
ioprio for NFS reads, though I vaguely wish there was a way to propagate
some sort of please-don't-cache-this hint across that channel too!)

  reply	other threads:[~2017-05-05 21:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02 10:54 what happened to the nifty ioprio cache hinting stuff? Nix
2017-05-02 17:26 ` Eric Wheeler
2017-05-05 21:41   ` Nix [this message]
2017-05-02 18:15 ` Kai Krakow
2017-05-05 21:48   ` Nix
2017-05-06 10:37     ` Kai Krakow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878tmbasn5.fsf@esperi.org.uk \
    --to=nix@esperi.org.uk \
    --cc=axboe@kernel.dk \
    --cc=bcache@lists.ewheeler.net \
    --cc=kai@kaishome.de \
    --cc=linux-bcache@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox