From: Nix <nix@esperi.org.uk>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: Kai Krakow <kai@kaishome.de>,
linux-bcache@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 1/3] bcache: introduce bcache sysfs entries for ioprio-based bypass/writeback hints
Date: Wed, 07 Oct 2020 13:43:26 +0100 [thread overview]
Message-ID: <87362q9pg1.fsf@esperi.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.11.2010070035310.27518@pop.dreamhost.com> (Eric Wheeler's message of "Wed, 7 Oct 2020 00:41:59 +0000 (UTC)")
On 7 Oct 2020, Eric Wheeler said:
> I always make my own cgroups with cgcreate, cgset, and cgexec. We're
> using centos7 which is all systemd and I've never had a problem:
Oh, maybe I'm panicking about nothing as usual then. Maybe this is all
ancient systemd bugs that were fixed roughly when the Americas split off
from Europe but which I've been worrying over without retesting ever
since. :)
> Something (hypothetically) like this:
> cgcreate -g blkio:/my_bcache_settings
> cgset -r blkio.bcache.bypass='read,write' my_bcache_settings
> cgset -r blkio.bcache.writeback='write,meta' my_bcache_settings
>
> Then all you need to do is run this which isn't all that different from an
> ionice invocation:
> cgexec -g blkio:my_bcache_settings /usr/local/bin/some-program
... if it's that easy, I have no objections :) actually that looks
significantly more expressive than what we have now.
--
NULL && (void)
next prev parent reply other threads:[~2020-10-07 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201003111056.14635-1-kai@kaishome.de>
[not found] ` <20201003111056.14635-2-kai@kaishome.de>
[not found] ` <87362ucen3.fsf@esperi.org.uk>
[not found] ` <CAC2ZOYt+ZMep=PT5FbQKiqZ0EE1f4+JJn=oTJUtQjLwGvy=KfQ@mail.gmail.com>
2020-10-05 19:41 ` [PATCH 1/3] bcache: introduce bcache sysfs entries for ioprio-based bypass/writeback hints Eric Wheeler
2020-10-06 12:28 ` Nix
2020-10-06 13:10 ` Kai Krakow
2020-10-06 16:34 ` Nix
2020-10-07 0:41 ` Eric Wheeler
2020-10-07 12:43 ` Nix [this message]
2020-10-07 20:35 ` Eric Wheeler
2020-10-08 10:45 ` 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=87362q9pg1.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=bcache@lists.ewheeler.net \
--cc=kai@kaishome.de \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).