From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from imap.thunk.org ([74.207.234.97]:38266 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966992AbeF1W7A (ORCPT ); Thu, 28 Jun 2018 18:59:00 -0400 Date: Thu, 28 Jun 2018 18:58:57 -0400 From: "Theodore Y. Ts'o" To: Steve French Cc: linux-fsdevel , LKML , samba-technical , CIFS Subject: Re: config files and how to have persistent Linux kernel Driver/File System configuration info saved Message-ID: <20180628225857.GB1231@thunk.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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