| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <bf2ed5d6-0e15-4e18-898e-317f9885099d@infradead.org> Date: Tue, 15 Apr 2025 08:35:51 -0700 From: Randy Dunlap <rdunlap@...radead.org> To: John Garry <john.g.garry@...cle.com>, brauner@...nel.org, djwong@...nel.org, hch@....de, viro@...iv.linux.org.uk, jack@...e.cz, cem@...nel.org Cc: linux-fsdevel@...r.kernel.org, dchinner@...hat.com, linux-xfs@...r.kernel.org, linux-kernel@...r.kernel.org, ojaswin@...ux.ibm.com, ritesh.list@...il.com, martin.petersen@...cle.com, linux-ext4@...r.kernel.org, linux-block@...r.kernel.org, catherine.hoang@...cle.com, linux-api@...r.kernel.org Subject: Re: [PATCH v7 14/14] xfs: allow sysadmins to specify a maximum atomic write limit at mount time On 4/15/25 5:14 AM, John Garry wrote: > diff --git a/Documentation/admin-guide/xfs.rst b/Documentation/admin-guide/xfs.rst > index b67772cf36d6..715019ec4f24 100644 > --- a/Documentation/admin-guide/xfs.rst > +++ b/Documentation/admin-guide/xfs.rst > @@ -143,6 +143,14 @@ When mounting an XFS filesystem, the following options are accepted. > optional, and the log section can be separate from the data > section or contained within it. > > + max_atomic_write=value > + Set the maximum size of an atomic write. The size may be > + specified in bytes, in kilobytes with a "k" suffix, in megabytes > + with a "m" suffix, or in gigabytes with a "g" suffix. > + > + The default value is to set the maximum io completion size Preferably I/O or IO > + to allow each CPU to handle one at a time. > + -- ~Randy
Powered by blists - more mailing lists