FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=stable%2F5 2005-06-10T08:41:56Z 2005-06-10T08:41:56Z Robert Watson rwatson@FreeBSD.org 2005-06-10T08:41:56Z urn:sha1:aba09a60fa7c18283e782b177153a2dff3898393 De-spl kern_connect(). Remove now unused 'int s' from spl(). 2005-05-11T21:54:44Z Maksim Yevmenkin emax@FreeBSD.org 2005-05-11T21:54:44Z urn:sha1:a47e52c295a42cc494de4006465fab8c34a7bc90 Change m_uiotombuf so it will accept offset at which data should be copied to the mbuf. Offset cannot exceed MHLEN bytes. This is currently used to fix Ethernet header alignment problem on alpha and sparc64. Also change all users of m_uiotombuf to pass proper offset. Reviewed by: jmg, sam Approved by: re 2005-03-09T18:59:20Z Alan Cox alc@FreeBSD.org 2005-03-09T18:59:20Z urn:sha1:209c5b1805e313309f03af1076a1a710d9940958 Introduce two new options, "CPU private" and "no wait", to sf_buf_alloc(). Change the spelling of the "catch" option to be consistent with the new options. Approved by: re (kensmith) 2005-02-27T02:51:39Z Jeff Roberson jeff@FreeBSD.org 2005-02-27T02:51:39Z urn:sha1:24641c3f59db7316f94574b0a32f934f65d21307 - filedesc locking cleanup. 2005-02-25T18:03:49Z Alan Cox alc@FreeBSD.org 2005-02-25T18:03:49Z urn:sha1:0cf65e6926e91064655c3fb89c9a935261790152 Modify the vm object locking in do_sendfile() so that the containing object is locked when vm_page_io_finish() is called on a page. MFC revision 1.203 Use VM_ALLOC_NOBUSY instead of calling vm_page_wakeup(). MFC revision 1.205 Eliminate unnecessary calls to vm_page_busy(). 2005-02-20T00:56:04Z Robert Watson rwatson@FreeBSD.org 2005-02-20T00:56:04Z urn:sha1:903faf0bbe14a5b47e0ba90607d9a2dfc82d3d3d date: 2005/02/17 13:00:23; author: rwatson; state: Exp; lines: +2 -2 In accept1(), extend coverage of the socket lock from just covering soref() to also covering the update of so_state. While no other user threads can update the socket state here as it's not yet hooked up to the file descriptor array yet, the protocol could also frob the socket state here, leading to a lost update to the so_state field. No reported instances of this bug (as yet). 2005-01-31T23:27:04Z Warner Losh imp@FreeBSD.org 2005-01-31T23:27:04Z urn:sha1:c9769f3ab5327a99909391e070c143e92ddc43ec 2004-11-20T02:09:48Z Robert Watson rwatson@FreeBSD.org 2004-11-20T02:09:48Z urn:sha1:a7b384ae4b06a5cde8312c73656aace77a56dc48 date: 2004/10/24 23:45:01; author: rwatson; state: Exp; lines: +87 -23 Move from using the socket reference count to the file reference count to prevent sockets from being garbage collected during socket-specific system calls. This is the same approach used in most VFS-specific system calls, as well as generic file descriptor system calls such as read() and write(). To do this, add a utility function getsock(), which is logically identical to getvnode() used for the same purpose in VFS. Unlike fgetsock(), it returns with the file reference count elevated, but no bump of the socket reference count. Replace matching calls to fputsock() with fdrop(). This change is made to all socket system calls other than sendfile() and accept(), but the approach should be applicable to those system calls also. This shaves about four mutex operations off of each of these system calls, including send() and recv() variants, adding about 1% to pps on minimal UDP packets for UP using netblast, and 4% on SMP. Reviewed by: pjd 2004-10-08T23:37:19Z Alan Cox alc@FreeBSD.org 2004-10-08T23:37:19Z urn:sha1:3b64e3a9ce38d7b15c610e4512526d5fb06e953e Add a SOCKBUF_LOCK() to a rarely executed path in do_sendfile(). Approved by: re (scottl) 2004-08-15T06:24:42Z John-Mark Gurney jmg@FreeBSD.org 2004-08-15T06:24:42Z urn:sha1:ad3b9257c2f09a6f1c0e56c1100aa4e43fb95e24 a more complete subsystem, and removes the knowlege of how things are implemented from the drivers. Include locking around filter ops, so a module like aio will know when not to be unloaded if there are outstanding knotes using it's filter ops. Currently, it uses the MTX_DUPOK even though it is not always safe to aquire duplicate locks. Witness currently doesn't support the ability to discover if a dup lock is ok (in some cases). Reviewed by: green, rwatson (both earlier versions)