[continued from previous message]
scheduled to them, but a prototype solution exists and is working. This means
that S0i3 can now be entered on the Framework 13 AMD Ryzen 7040 series laptops,
albeit only on my working 14.1 branch. This does not work on -CURRENT yet.
The amdgpio driver (for the AMD GPIO controller) has been extended to service
all GPIO interrupts and suspend the controller, as that was potentially a
blocker for the CPU to enter S0i3. Nothing is being done with these GPIO
interrupts at the moment as FreeBSD does not have the infrastructure for device
drivers to register these interrupts on x86 yet.
The SMU idlemask is also now being exported as a sysctl now
(dev.amdsmu.0.idlemask), the value of which is not documented and is mostly to
help AMD debug issues with S0i3 entry on FreeBSD on their side.
A pre-built image is being built to aid in easily testing S0i3 entry on
machines.
With respect to the links, the blog post entry is outdated. A talk was given
about this at BSDCan 2025 too, but it has yet to be uploaded as a standalone
video; it will be included in the next status report.
Sponsor: The FreeBSD Foundation
━━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━
Named attribute support (Solaris style extended attributes)
Contact: Rick Macklem
Named attributes is the NFSv4 term for what is also known as Solaris style
extended attributes. Since ZFS has its origins in Solaris, the wiring for these
exists in OpenZFS. This little project consists of connecting that wiring up.
This is not intended to replace the extended attribute support already in
FreeBSD. It provides an alternate mechanism for manipulating extended
attributes that will be supported for ZFS and NFSv4. There are a few reasons I
think this could be useful (as indicated via email discussion). This mechanism
allows for extended attributes as large as any regular file, which can be
partially updated. Some NFSv4 clients, such as MacOS and Windows, can use these
extended attributes but not the FreeBSD/Linux style ones. (I think MacOS calls
these extended attributes fork files and Windows calls them alternate data
streams.) There is software, such as bash, that know how to manipulate these
extended attributes.
The fundamental difference is that this mechanism provides a directory that is
not in the file system’s namespace, but is associated with a file object.
This
named attribute directory can then be read via readdir(3) to get the list of
extended attributes, which are really just regular files. These extended
attributes are then read/written like any regular file.
The top level system call interface is open(2)/openat(2) with the new
O_NAMEDATTR flag (called O_XATTR on Solaris).
Most of the work has been committed to FreeBSD’s main for FreeBSD 15. Once
the
ZFS patch makes it through review and gets pulled into OpenZFS, the ZFS and
NFSv4 support should work. There are also a couple of manual pages currently
under review in phabricator.
The main thing left to do is update libarchive/tar so that large extended
attributes can be archived/retrieved. (The current FreeBSD extended attribute
mechanism is supported by libarchive, but will have size constraints.)
━━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━
Packrat — NFS client caching on non-volatile storage
Contact: Rick Macklem
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 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 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.
The patch is getting stable now, but I am not sure if it will be ready for
inclusion in FreeBSD 15 as an experimental feature enabled via a new mount
option called "packrat".
The main thing I still need to do is code a writeback kernel thread. Right now,
dirty chunks stored on client local non-volatile storage get written back to
the NFSv4.1/4.2 server upon umount. 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, particularly in WAN situations, such as
a mobile laptop.
There is still work to be done, particularly with respect to recovery of
delegations after a NFSv4.1/4.2 client restart.
━━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━
LinuxKPI 802.11 and Native Wireless Update
Links:
802.11ac support URL:https://github.com/FreeBSDFoundation/proj-laptop/issues/33
LinuxKPI TKIP and GCMP support URL:https://github.com/FreeBSDFou
dation/proj-laptop/issues/64
LinuxKPI wireless suspend and resume URL:https://github.com/Free
SDFoundation/proj-laptop/issues/58
MediaTek mt76 PCI driver support URL:https://github.com/FreeBSDF
undation/proj-laptop/issues/66
802.11ax support URL:https://github.com/FreeBSDFoundation/proj-laptop/issues/34
net80211 updates URL:https://github.com/FreeBSDFoundation/proj-laptop/issues/79
Tracked wireless PRs URL:https://bugs.freebsd.org/bugzilla/showd
pendencytree.cgi?id=277512&hide_resolved=1
Contact: Bjoern A. Zeeb
Contact: The FreeBSD wireless mailing list
This report focuses on the efforts using permissively licensed Linux wireless
drivers, mostly unmodified, on FreeBSD, as well as preparing the native
net80211 stack for support of newer standards.
As announced iwlwififw(4) was removed from the source tree in favor of a ports/
package based solution. Users are asked to use fwget(8) to automatically
install the firmware along with any possible configuration.
Support for wlan_tkip(4) was added to linuxkpi(4) but has to be manually
enabled. wlan_gcmp(4) support for linuxkpi(4) followed later and is available
from FreeBSD 15 onward.
FreeBSD 14.3-RELEASE is the first release with VHT (802.11ac) support
[continued in next message]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
