Date: Tue, 24 Jun 2025 10:51:54 GMT From: Maxim Konovalov <maxim@FreeBSD.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org Subject: git: 80394bc1a9 - main - Status/2025Q2: spell Message-ID: <202506241051.55OAps1W034614@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by maxim: URL: https://cgit.FreeBSD.org/doc/commit/?id=80394bc1a9845c318671c3e7ea322ddb0f3bc390 commit 80394bc1a9845c318671c3e7ea322ddb0f3bc390 Author: Maxim Konovalov <maxim@FreeBSD.org> AuthorDate: 2025-06-24 10:50:05 +0000 Commit: Maxim Konovalov <maxim@FreeBSD.org> CommitDate: 2025-06-24 10:50:05 +0000 Status/2025Q2: spell --- website/content/en/status/report-2025-04-2025-06/packrat.adoc | 8 ++++---- .../content/en/status/report-2025-04-2025-06/ports-security.adoc | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/website/content/en/status/report-2025-04-2025-06/packrat.adoc b/website/content/en/status/report-2025-04-2025-06/packrat.adoc index 7ceaaebd22..f496bccc9c 100644 --- a/website/content/en/status/report-2025-04-2025-06/packrat.adoc +++ b/website/content/en/status/report-2025-04-2025-06/packrat.adoc @@ -4,9 +4,9 @@ Contact: Rick Macklem <rmacklem@freebsd.org> NFSv4.1/4.2 provides support for a feature called delegations. When a NFSv4.1/4.2 client holds a delegation, the client has certain rights to a file, including a guarantee that no other client will make changes to the file unless the delegation is recalled. -As such, when a client holds a delegation for a file, it can agressively cache the file's data, knowing that it will not be modified by other clients until it returns the delegation. +As such, when a client holds a delegation for a file, it can aggressively cache the file's data, knowing that it will not be modified by other clients until it returns the delegation. -This project is intended to allow the NFSv4.1/4.2 client to agressively cache file data on client local non-volatile storage, when the client holds a delegation for the file. +This project is intended to allow the NFSv4.1/4.2 client to aggressively cache file data on client local non-volatile storage, when the client holds a delegation for the file. I created a patch long ago to try and do this for NFSv4.0, but it was never at a stage where it was worth using. This project is a complete rewrite of the patch, done in part because NFSv4.1/4.2 plus other recent NFSv4 related changes makes doing this more feasible. @@ -18,6 +18,6 @@ This can result in the umount taking a long time (as in many minutes). To alleviate this, I am planning on implementing a writeback kernel process that will walk the non-volatile storage and write the dirty chunks back. The trick is to make it aggressive enough that most dirty chunks have been written back when a umount is done, but not so aggressive that it impedes the performance of synchronous NFSv4.1/4.2 RPCs. -This will be very much an experimental feature, but it is hoped it will allow NFS mounts to be used more effectively, particularily in WAN situations, such as a mobile laptop. +This will be very much an experimental feature, but it is hoped it will allow NFS mounts to be used more effectively, particularly in WAN situations, such as a mobile laptop. -There is still work to be done, particularily with respect to recovery of delegations after a NFSv4.1/4.2 client restart. +There is still work to be done, particularly with respect to recovery of delegations after a NFSv4.1/4.2 client restart. diff --git a/website/content/en/status/report-2025-04-2025-06/ports-security.adoc b/website/content/en/status/report-2025-04-2025-06/ports-security.adoc index d4b4211b77..8fb04f26d6 100644 --- a/website/content/en/status/report-2025-04-2025-06/ports-security.adoc +++ b/website/content/en/status/report-2025-04-2025-06/ports-security.adoc @@ -21,4 +21,4 @@ Zero call-used registers at function return to increase program security by eith This depends upon support from the compiler for a given architecture. This is disabled for python ports; currently there are issues. -The blog post referenced in the links section explains how to use them, how to exclude certain ports if needed, and provides a more detailed explaination of those 3 new features along the already existing build-time security options of the Ports Collection and the basesystem build. +The blog post referenced in the links section explains how to use them, how to exclude certain ports if needed, and provides a more detailed explanation of those 3 new features along the already existing build-time security options of the Ports Collection and the basesystem build.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202506241051.55OAps1W034614>