FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F8.1.0 2010-03-22T09:29:56Z 2010-03-22T09:29:56Z Konstantin Belousov kib@FreeBSD.org 2010-03-22T09:29:56Z urn:sha1:1b90b87fbad469d067fd29debee76d04b4933b14 Teach procstat(1) to display some information about signal disposition and pending/blocked status for signals. MFC r204880: Add file forgotten in r204879. 2009-08-13T14:38:09Z Robert Watson rwatson@FreeBSD.org 2009-08-13T14:38:09Z urn:sha1:7a34e29bc6de21da6911e67c17ad72085702c4ab Update procstat(1) for the fact that devfs paths are no longer unsupported. Approved by: re (kib) 2009-07-24T19:12:19Z Brooks Davis brooks@FreeBSD.org 2009-07-24T19:12:19Z urn:sha1:254d03c5081f56a7d77a9c49b95a08ee107989a5 ability to retrieve the group list of each process. Modify procstat's -s option to query this mib when the kinfo_proc reports that the field has been truncated. If the mib does not exist, fall back to the truncated list. Reviewed by: rwatson Approved by: re (kib) MFC after: 2 weeks 2009-07-24T13:50:29Z John Baldwin jhb@FreeBSD.org 2009-07-24T13:50:29Z urn:sha1:013818111a1477055223a69d538ebcd1c23b955e a device pager (OBJT_DEVICE) object in that it uses fictitious pages to provide aliases to other memory addresses. The primary difference is that it uses an sglist(9) to determine the physical addresses for a given offset into the object instead of invoking the d_mmap() method in a device driver. Reviewed by: alc Approved by: re (kensmith) MFC after: 2 weeks 2008-12-29T18:58:22Z Robert Watson rwatson@FreeBSD.org 2008-12-29T18:58:22Z urn:sha1:e1f323f350084227fe4c2b8eb5e47fcbf2d3c952 include of param.h can be removed from audit.h. MFC after: 3 weeks 2008-12-19T16:56:49Z Wesley Shields wxs@FreeBSD.org 2008-12-19T16:56:49Z urn:sha1:d5db4444c3f6b400c956bb5faa267829f904af32 Approved by: rwatson 2008-12-19T06:50:15Z Joe Marcus Clarke marcus@FreeBSD.org 2008-12-19T06:50:15Z urn:sha1:08afefa8141d3414260b63956d9d77ed94f0c694 owned by the current user. If kinfo_getfile() or kinfo_getvmmap() return NULL, simply exit, and do not try and derefernce the memory. Reviewed by: peter Approved by: peter 2008-12-02T15:08:33Z Peter Wemm peter@FreeBSD.org 2008-12-02T15:08:33Z urn:sha1:41fbf4374b6f202cd5d017f87cbc9df7179c5a5d 2008-12-02T06:50:26Z Peter Wemm peter@FreeBSD.org 2008-12-02T06:50:26Z urn:sha1:43151ee6cfcbe0b6e38e49de940ae9e58fe934af This changes struct kinfo_filedesc and kinfo_vmentry such that they are same on both 32 and 64 bit platforms like i386/amd64 and won't require sysctl wrapping. Two new OIDs are assigned. The old ones are available under COMPAT_FREEBSD7 - but it isn't that simple. The superceded interface was never actually released on 7.x. The other main change is to pack the data passed to userland via the sysctl. kf_structsize and kve_structsize are reduced for the copyout. If you have a process with 100,000+ sockets open, the unpacked records require a 132MB+ copyout. With packing, it is "only" ~35MB. (Still seriously unpleasant, but not quite as devastating). A similar problem exists for the vmentry structure - have lots and lots of shared libraries and small mmaps and its copyout gets expensive too. My immediate problem is valgrind. It traditionally achieves this functionality by parsing procfs output, in a packed format. Secondly, when tracing 32 bit binaries on amd64 under valgrind, it uses a cross compiled 32 bit binary which ran directly into the differing data structures in 32 vs 64 bit mode. (valgrind uses this to track file descriptor operations and this therefore affected every single 32 bit binary) I've added two utility functions to libutil to unpack the structures into a fixed record length and to make it a little more convenient to use. 2008-08-20T08:31:58Z Ed Schouten ed@FreeBSD.org 2008-08-20T08:31:58Z urn:sha1:bc093719ca478fe10b938cef32c30b528042cbcd The last half year I've been working on a replacement TTY layer for the FreeBSD kernel. The new TTY layer was designed to improve the following: - Improved driver model: The old TTY layer has a driver model that is not abstract enough to make it friendly to use. A good example is the output path, where the device drivers directly access the output buffers. This means that an in-kernel PPP implementation must always convert network buffers into TTY buffers. If a PPP implementation would be built on top of the new TTY layer (still needs a hooks layer, though), it would allow the PPP implementation to directly hand the data to the TTY driver. - Improved hotplugging: With the old TTY layer, it isn't entirely safe to destroy TTY's from the system. This implementation has a two-step destructing design, where the driver first abandons the TTY. After all threads have left the TTY, the TTY layer calls a routine in the driver, which can be used to free resources (unit numbers, etc). The pts(4) driver also implements this feature, which means posix_openpt() will now return PTY's that are created on the fly. - Improved performance: One of the major improvements is the per-TTY mutex, which is expected to improve scalability when compared to the old Giant locking. Another change is the unbuffered copying to userspace, which is both used on TTY device nodes and PTY masters. Upgrading should be quite straightforward. Unlike previous versions, existing kernel configuration files do not need to be changed, except when they reference device drivers that are listed in UPDATING. Obtained from: //depot/projects/mpsafetty/... Approved by: philip (ex-mentor) Discussed: on the lists, at BSDCan, at the DevSummit Sponsored by: Snow B.V., the Netherlands dcons(4) fixed by: kan