From: gius db <giusdbg@gmail.com>
To: linux-bcache@vger.kernel.org
Subject: Re: Throttling performance due to backing device latency
Date: Wed, 22 Mar 2023 08:57:40 +0100 [thread overview]
Message-ID: <CAO6aweO4tbREeen10rQP46SyJNZTx+WN2J5sdTiihJhjRn4eZA@mail.gmail.com> (raw)
In-Reply-To: <CAO6aweOvLUP0L+DXwJEpbFJ_mF0E44pWcLzXoXvAi4MGPBkFBg@mail.gmail.com>
Hi.
I'm (negatively) surprised by the non-reaction from the developers
(and everyone).
The point and the proposed solution is not esoteric, it doesn't
concern strange or complicated things, but something trivial and
evident (when using writeback, cache performance is lost unnecessarily
and without warning).
Okay, I'll be wrong, and anyway bcache for me, it's useful, it works
well, I can fix it.
next prev parent reply other threads:[~2023-03-22 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 13:28 Throttling performance due to backing device latency gius db
2023-03-22 7:57 ` gius db [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-07 11:43 benard_bsc
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=CAO6aweO4tbREeen10rQP46SyJNZTx+WN2J5sdTiihJhjRn4eZA@mail.gmail.com \
--to=giusdbg@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).