From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Steve French <smfrench@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
samba-technical <samba-technical@lists.samba.org>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: config files and how to have persistent Linux kernel Driver/File System configuration info saved
Date: Thu, 28 Jun 2018 18:58:57 -0400 [thread overview]
Message-ID: <20180628225857.GB1231@thunk.org> (raw)
In-Reply-To: <CAH2r5msV1hBAGgqtMFh6P=OGPV3RKjVAER=5bg-6Y+vW5BEJwQ@mail.gmail.com>
On Thu, Jun 28, 2018 at 05:37:15PM -0500, Steve French wrote:
> Ronnie brought up an interesting point about the problems consistently
> configuring file systems (or any Linux module for that matter) so that
> reboot doesn't wipe away security or performance tuning changes.
In general it's considered best practice to make the file system
auto-tune itself as much as possible, because the sad fact is that
99.9999% of the customers aren't going to bother to add any tuning
parameters. So there hasn't been a push to try to create something
more complex, because it's generally not needed.
Settings via /sys/fs/ext4 are generally for developers as they try to
understand how things work, so they can improve the file systems
defaults / auto-tuning algorithms.
- Ted
next prev parent reply other threads:[~2018-06-28 22:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 22:37 config files and how to have persistent Linux kernel Driver/File System configuration info saved Steve French
2018-06-28 22:58 ` Theodore Y. Ts'o [this message]
2018-06-28 23:21 ` ronnie sahlberg
2018-06-28 23:24 ` Steve French
2018-06-29 4:44 ` Dave Chinner
2018-06-29 19:53 ` Steve French
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=20180628225857.GB1231@thunk.org \
--to=tytso@mit.edu \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@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).