From: Wols Lists <antlists@youngman.org.uk>
To: Roger Heflin <rogerheflin@gmail.com>, Ram Ramesh <rramesh2400@gmail.com>
Cc: Nix <nix@esperi.org.uk>, Drew <drew.kay@gmail.com>,
Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: Best way to add caching to a new raid setup.
Date: Mon, 14 Sep 2020 16:08:31 +0100 [thread overview]
Message-ID: <5F5F876F.8070306@youngman.org.uk> (raw)
In-Reply-To: <CAAMCDecjgMvXPPwhWZKi5VmJEPeLzFkUuQ2M_EwxnDxd=ntSZA@mail.gmail.com>
On 14/09/20 15:48, Roger Heflin wrote:
> It should be noted that mythtv is a badly behaved IO application, it
> does a lot of sync calls that effectively for the most part makes
> linux's write cache small.
Sounds like the devs need reminding of the early days of ext4. Iiuc, if
that ran on an early ext4 you wouldn't have got ANY successful
recordings AT ALL.
At an absolute minimum, that sort of behaviour needs to be configurable,
because if the user is running mythtv on anything other than a dedicated
machine then it's going to kill performance for anything else.
Cheers,
Wol
next prev parent reply other threads:[~2020-09-14 15:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16cee7f2-38d9-13c8-4342-4562be68930b.ref@verizon.net>
2020-08-28 2:31 ` Best way to add caching to a new raid setup R. Ramesh
2020-08-28 3:05 ` Peter Grandi
2020-08-28 3:19 ` Ram Ramesh
2020-08-28 15:26 ` antlists
2020-08-28 17:25 ` Ram Ramesh
2020-08-28 22:12 ` antlists
2020-08-28 22:40 ` Ram Ramesh
2020-08-28 22:59 ` antlists
2020-08-29 3:08 ` R. Ramesh
2020-08-29 5:02 ` Roman Mamedov
2020-08-29 20:48 ` Ram Ramesh
2020-08-29 21:26 ` Roger Heflin
2020-08-30 0:56 ` Ram Ramesh
2020-08-30 15:42 ` Roger Heflin
2020-08-30 17:19 ` Ram Ramesh
2020-09-11 18:39 ` R. Ramesh
2020-09-11 20:37 ` Roger Heflin
2020-09-11 22:41 ` Ram Ramesh
2020-08-29 0:01 ` Roger Heflin
2020-08-29 3:12 ` R. Ramesh
2020-08-29 22:36 ` Drew
2020-09-01 16:12 ` Ram Ramesh
2020-09-01 17:01 ` Kai Stian Olstad
2020-09-02 18:17 ` Ram Ramesh
2020-09-14 11:40 ` Nix
2020-09-14 14:32 ` Ram Ramesh
2020-09-14 14:48 ` Roger Heflin
2020-09-14 15:08 ` Wols Lists [this message]
2020-08-31 19:20 ` Nix
2020-08-28 17:46 ` Roman Mamedov
2020-08-28 20:39 ` Ram Ramesh
2020-08-29 15:34 ` antlists
2020-08-29 15:57 ` Roman Mamedov
2020-08-29 16:26 ` Roger Heflin
2020-08-29 20:45 ` Ram Ramesh
2020-08-30 22:16 ` Michal Soltys
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=5F5F876F.8070306@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=drew.kay@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=nix@esperi.org.uk \
--cc=rogerheflin@gmail.com \
--cc=rramesh2400@gmail.com \
/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).