FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=releng%2F13.3 2011-04-25T22:22:51Z 2011-04-25T22:22:51Z Rick Macklem rmacklem@FreeBSD.org 2011-04-25T22:22:51Z urn:sha1:7c208ed659437ef984f2bb98bdc20fa5cfdebefc set the f_flags field of "struct statfs". This had the interesting effect of making the NFSv4 mounts "disappear" after r221014, since NFSMNT_NFSV4 and MNT_IGNORE became the same bit. Move the files used for a diskless NFS root from sys/nfsclient to sys/nfs in preparation for them to be used by both NFS clients. Also, move the declaration of the three global data structures from sys/nfsclient/nfs_vfsops.c to sys/nfs/nfs_diskless.c so that they are defined when either client uses them. Reviewed by: jhb MFC after: 2 weeks 2011-02-16T21:29:13Z Bjoern A. Zeeb bz@FreeBSD.org 2011-02-16T21:29:13Z urn:sha1:1fb51a12f24a4d5ffd7d105589ed8e002ad67320 VNET socket push back: try to minimize the number of places where we have to switch vnets and narrow down the time we stay switched. Add assertions to the socket code to catch possibly unset vnets as seen in r204147. While this reduces the number of vnet recursion in some places like NFS, POSIX local sockets and some netgraph, .. recursions are impossible to fix. The current expectations are documented at the beginning of uipc_socket.c along with the other information there. Sponsored by: The FreeBSD Foundation Sponsored by: CK Software GmbH Reviewed by: jhb Tested by: zec Tested by: Mikolaj Golub (to.my.trociny gmail.com) MFC after: 2 weeks 2010-09-01T23:51:07Z Rick Macklem rmacklem@FreeBSD.org 2010-09-01T23:51:07Z urn:sha1:090c02f8bd37fd278f8c4e26fc87b15578c80b7e boot.nfsroot.nfshandlelen and set the diskless root fs to use NFSv3 and this file handle length when it is set. If this environment variable is not set, the diskless root fs will use NFSv2 and the same defaults as before. This fixes the problem where the diskless nfs root fs had to be on a FreeBSD server for NFSv3 to work, because it did not know the correct file handle length and assumed the size used by FreeBSD. Until pxeboot and loader are replaced by ones built from commits coming soon, boot.nfsroot.nfshandlelen will not be set by them and the diskless root fs will use NFSv2 unless the /etc/fstab entry has the "nfsv3" option specified. Tested by: danny at cs.huji.ac.il MFC after: 2 weeks 2009-08-01T19:26:27Z Robert Watson rwatson@FreeBSD.org 2009-08-01T19:26:27Z urn:sha1:530c006014fae95c670f4b699fef8bb93034bc6d vnet.h, we now use jails (rather than vimages) as the abstraction for virtualization management, and what remained was specific to virtual network stacks. Minor cleanups are done in the process, and comments updated to reflect these changes. Reviewed by: bz Approved by: re (vimage blanket) 2009-07-14T22:48:30Z Robert Watson rwatson@FreeBSD.org 2009-07-14T22:48:30Z urn:sha1:eddfbb763ded6b5f6777335142be9a0edab628bb (DPCPU), as suggested by Peter Wemm, and implement a new per-virtual network stack memory allocator. Modify vnet to use the allocator instead of monolithic global container structures (vinet, ...). This change solves many binary compatibility problems associated with VIMAGE, and restores ELF symbols for virtualized global variables. Each virtualized global variable exists as a "reference copy", and also once per virtual network stack. Virtualized global variables are tagged at compile-time, placing the in a special linker set, which is loaded into a contiguous region of kernel memory. Virtualized global variables in the base kernel are linked as normal, but those in modules are copied and relocated to a reserved portion of the kernel's vnet region with the help of a the kernel linker. Virtualized global variables exist in per-vnet memory set up when the network stack instance is created, and are initialized statically from the reference copy. Run-time access occurs via an accessor macro, which converts from the current vnet and requested symbol to a per-vnet address. When "options VIMAGE" is not compiled into the kernel, normal global ELF symbols will be used instead and indirection is avoided. This change restores static initialization for network stack global variables, restores support for non-global symbols and types, eliminates the need for many subsystem constructors, eliminates large per-subsystem structures that caused many binary compatibility issues both for monitoring applications (netstat) and kernel modules, removes the per-function INIT_VNET_*() macros throughout the stack, eliminates the need for vnet_symmap ksym(2) munging, and eliminates duplicate definitions of virtualized globals under VIMAGE_GLOBALS. Bump __FreeBSD_version and update UPDATING. Portions submitted by: bz Reviewed by: bz, zec Discussed with: gnn, jamie, jeff, jhb, julian, sam Suggested by: peter Approved by: re (kensmith) 2009-06-30T19:03:27Z Doug Rabson dfr@FreeBSD.org 2009-06-30T19:03:27Z urn:sha1:b49a2b39fdac2fd3489a6e579946c87104a51f33 Approved by: re 2009-06-23T17:03:45Z Bjoern A. Zeeb bz@FreeBSD.org 2009-06-23T17:03:45Z urn:sha1:5736e6fb9d15b95ee15c93c75e67222183a14b1d a lot of files no longer need route.h either. Garbage collect them. While here remove now unneeded vnet.h #includes as well. 2009-06-08T19:57:35Z Bjoern A. Zeeb bz@FreeBSD.org 2009-06-08T19:57:35Z urn:sha1:8d8bc0182ea6f8f85409e76e53053487c7d23a84 the ROUTETABLES kernel option thus there is no need to include opt_route.h anymore in all consumers of vnet.h and no longer depend on it for module builds. Remove the hidden include in flowtable.h as well and leave the two explicit #includes in ip_input.c and ip_output.c. 2009-05-22T12:35:12Z Robert Watson rwatson@FreeBSD.org 2009-05-22T12:35:12Z urn:sha1:86ce6a83d16fdedede88990ffe1d85ad83d8e7c8 prior to 8.0-RELEASE. Rick Macklem's new and more feature-rich NFSv234 client and server are replacing it. Discussed with: rmacklem 2009-02-27T14:12:05Z Bjoern A. Zeeb bz@FreeBSD.org 2009-02-27T14:12:05Z urn:sha1:33553d6e997f102da7a5f27d534b3ee57beb0a87 net/route.h. Remove the hidden include of opt_route.h and net/route.h from net/vnet.h. We need to make sure that both opt_route.h and net/route.h are included before net/vnet.h because of the way MRT figures out the number of FIBs from the kernel option. If we do not, we end up with the default number of 1 when including net/vnet.h and array sizes are wrong. This does not change the list of files which depend on opt_route.h but we can identify them now more easily.