public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Goran <via-bcache@pvgoran.name>
To: Eric Wheeler <linux-bcache@vger.kernel.org>
Subject: Re: [PATCH 1/2] bcache: introduce ioprio-based bypass/writeback hints
Date: Tue, 27 Sep 2016 08:43:09 +0700	[thread overview]
Message-ID: <1610652744.20160927084309@pvgoran.name> (raw)
In-Reply-To: <S1754035AbcIZXgt/20160926233649Z+17415@vger.kernel.org>

Hello Eric,

Tuesday, September 27, 2016, 6:17:22 AM, you wrote:

> Add support to bcache hinting functions and sysfs to hint by the ioprio of
> 'current' which can be configured with `ionice`.

> Cache hinting is configurable by writing 'class,level' pairs to sysfs.
> These are the defaults:
>         echo 2,7 > /sys/block/bcache0/bcache/ioprio_bypass
>         echo 2,0 > /sys/block/bcache0/bcache/ioprio_writeback

> (-p) IO Class    (-n) Class level       Action
> -----------------------------------------------------
> (1) Realtime      0-7                           Writeback
> (2) Best-effort     0                           Writeback
> (2) Best-effort   1-6                           Original bcache logic
> (2) Best-effort     7                           Bypass cache
> (3) Idle          n/a                           Bypass cache

Not sure it's a good idea, at all. If I set cache policy to, say,
write-through, then I expect write-back to never happen, regardless of what
userspace does with IO priority.

Similarly, using low IO priority (idle or best effort-7) should not make IO
*slow regardless of any other IO load* (which would happen if cache is
completely bypassed).

Right now, it looks to me as inappropriate mixing of different concepts.
Unless I fail to understand something.

Pavel Goran
  

  reply	other threads:[~2016-09-27  1:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26 23:17 [PATCH 1/2] bcache: introduce ioprio-based bypass/writeback hints Eric Wheeler
2016-09-27  1:43 ` Pavel Goran [this message]
2016-09-27  2:43   ` Kai Krakow
2016-09-28 18:21     ` Eric Wheeler
2016-09-29  6:57       ` Re[2]: " Pavel Goran
2016-09-29 18:31         ` Eric Wheeler
2016-09-29 18:34         ` Kai Krakow
2016-09-29 22:50           ` Eric Wheeler
2016-09-28 19:26 ` Kai Krakow
2016-09-28 21:38   ` Eric Wheeler
2016-09-29  2:19     ` 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=1610652744.20160927084309@pvgoran.name \
    --to=via-bcache@pvgoran.name \
    --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