Date: Mon, 11 Mar 2024 11:43:17 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Alexander Leidinger <Alexander@leidinger.net> Cc: current@freebsd.org Subject: Re: Reason why "nocache" option is not displayed in "mount"? Message-ID: <Ze7SNT-2KTs4wWgd@kib.kiev.ua> In-Reply-To: <720dc441819f0074362631b11a71f7de@Leidinger.net> References: <Ze3sMj6jf3upY3_G@kib.kiev.ua> <20240310215051.EC14296B7@freefall.freebsd.org> <Ze4ssbRm615OBQA3@kib.kiev.ua> <720dc441819f0074362631b11a71f7de@Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 11, 2024 at 09:03:38AM +0100, Alexander Leidinger wrote: > Am 2024-03-10 22:57, schrieb Konstantin Belousov: > > > We are already low on the free bits in the flags, even after expanding > > them > > to 64bit. More, there are useful common fs services continuously > > consuming > > that flags, e.g. the recent NFS TLS options. > > > > I object against using the flags for absolutely not important things, > > like > > this nullfs "cache" option. > > > > In long term, we would have to export nmount(2) strings since bits in > > flags are finite, but I prefer to delay it as much as possible. > > Why do you want to delay this? Personal priorities, or technical reasons? Because it is a lot of work which is currently not needed and where I will need to participate.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Ze7SNT-2KTs4wWgd>