All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Ferdinand <bcache@mfedv.net>
To: Coly Li <colyli@suse.de>
Cc: "linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: Input requirement for persistent configuration items in bcache
Date: Sun, 5 Jul 2020 11:12:14 +0200	[thread overview]
Message-ID: <20200705091214.GL14425@xoff> (raw)
In-Reply-To: <0fe47cd9-ffa0-b440-44ca-6ed9419dfb01@suse.de>

On Sun, Jul 05, 2020 at 12:45:41PM +0800, Coly Li wrote:
> While I am thinking about this, I do appreciate your help about the
> input on which configuration item should be stored in the on-disk
> superblock.

Hi,

my use case is rather limited, all my bcache devices run in writeback
mode, and the only parameters I keep playing with are writeback_percent
and sequential_cutoff.

My short list of favourites:

   - cache_mode
   - writeback_percent
   - sequential_cutoff

But I vaguely remember that I used rebooting as last resort after too
much fiddling with tunables; persisting them in the superblock means
losing this reset-to-defaults method. Would be nice to have some other
way of resetting.

An alternative to modifying the superblock might be something
more out-of-band like iptables does with iptables-save and
iptables-restore: convert current settings to text, e.g. on shutdown or
at regular intervals, and restore settings on boot from this text file.

Regards
Matthias

  reply	other threads:[~2020-07-05  9:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05  4:45 Input requirement for persistent configuration items in bcache Coly Li
2020-07-05  9:12 ` Matthias Ferdinand [this message]
2020-07-05 10:23   ` Coly Li
  -- strict thread matches above, loose matches on Subject: below --
2020-06-22  8:01 Coly Li

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=20200705091214.GL14425@xoff \
    --to=bcache@mfedv.net \
    --cc=colyli@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.