cc3116a938
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
63 lines
2.2 KiB
Plaintext
63 lines
2.2 KiB
Plaintext
#
|
|
# SKI -- Kernel configuration file for FreeBSD/ia64 running in the HP
|
|
# SKI simulator
|
|
#
|
|
# For more information on this file, please read the handbook section on
|
|
# Kernel Configuration Files:
|
|
#
|
|
# http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
|
|
#
|
|
# The handbook is also available locally in /usr/share/doc/handbook
|
|
# if you've installed the doc distribution, otherwise always see the
|
|
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
|
|
# latest information.
|
|
#
|
|
# An exhaustive list of options and more detailed explanations of the
|
|
# device lines is also present in the ../../conf/NOTES and NOTES files.
|
|
# If you are in doubt as to the purpose or necessity of a line, check
|
|
# first in NOTES.
|
|
#
|
|
# $FreeBSD$
|
|
|
|
cpu ITANIUM
|
|
ident SKI
|
|
|
|
makeoptions DEBUG=-g # Build kernel with debug information.
|
|
makeoptions NO_MODULES=yes # Don't build any modules.
|
|
|
|
options DDB # Support DDB
|
|
options FFS # Berkeley Fast Filesystem
|
|
options GDB # Support remote GDB
|
|
options INET # InterNETworking
|
|
options INET6 # IPv6 communications protocols
|
|
options KDB # Enable kernel debugger support
|
|
options KTRACE # ktrace(1) syscall trace support
|
|
options MD_ROOT # MD usable as root device
|
|
options PROCFS # Process filesystem (/proc)
|
|
options PSEUDOFS # Pseudo-filesystem framework
|
|
#options SCHED_4BSD # 4BSD scheduler
|
|
options SCHED_ULE # ULE scheduler
|
|
options SKI # Include SKI support code
|
|
options SOFTUPDATES # Enable FFS soft updates support
|
|
options SYSVMSG # SYSV-style message queues
|
|
options SYSVSEM # SYSV-style semaphores
|
|
options SYSVSHM # SYSV-style shared memory
|
|
options UFS_ACL # Support for access control lists
|
|
options UFS_DIRHASH # Hash-based directory lookup scheme
|
|
options _KPOSIX_PRIORITY_SCHEDULING # Posix P1003_1B RT extensions
|
|
|
|
# Various "busses"
|
|
device pci # PCI bus support
|
|
|
|
# Various (pseudo) devices
|
|
device ether # Ethernet support
|
|
device loop # Network loopback
|
|
device md # Memory "disks"
|
|
device pty # BSD-style compatibility pseudo ttys
|
|
device random # Entropy device
|
|
device tun # Packet tunnel.
|
|
|
|
# The `bpf' device enables the Berkeley Packet Filter.
|
|
# Be aware of the administrative consequences of enabling this!
|
|
device bpf # Berkeley packet filter
|