1994-05-26 05:23:31 +00:00
|
|
|
.\" Copyright (c) 1980, 1991, 1993, 1994
|
|
|
|
.\" The Regents of the University of California. All rights reserved.
|
2002-07-31 12:43:17 +00:00
|
|
|
.\" Copyright (c) 2002 Networks Associates Technology, Inc.
|
|
|
|
.\" All rights reserved.
|
|
|
|
.\"
|
|
|
|
.\" Portions of this software was developed for the FreeBSD Project by
|
|
|
|
.\" ThinkSec AS and NAI Labs, the Security Research Division of Network
|
|
|
|
.\" Associates, Inc. under DARPA/SPAWAR contract N66001-01-C-8035
|
|
|
|
.\" ("CBOSS"), as part of the DARPA CHATS research program.
|
1994-05-26 05:23:31 +00:00
|
|
|
.\"
|
|
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
|
|
.\" modification, are permitted provided that the following conditions
|
|
|
|
.\" are met:
|
|
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
|
|
.\" 4. Neither the name of the University nor the names of its contributors
|
|
|
|
.\" may be used to endorse or promote products derived from this software
|
|
|
|
.\" without specific prior written permission.
|
|
|
|
.\"
|
|
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
.\" SUCH DAMAGE.
|
|
|
|
.\"
|
1997-03-11 13:00:41 +00:00
|
|
|
.\" @(#)pstat.8 8.5 (Berkeley) 5/13/94
|
1999-08-28 01:35:59 +00:00
|
|
|
.\" $FreeBSD$
|
1994-05-26 05:23:31 +00:00
|
|
|
.\"
|
Integrate the new MPSAFE TTY layer to the FreeBSD operating system.
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
2008-08-20 08:31:58 +00:00
|
|
|
.Dd August 20, 2008
|
1994-05-26 05:23:31 +00:00
|
|
|
.Dt PSTAT 8
|
2001-07-10 15:12:08 +00:00
|
|
|
.Os
|
1994-05-26 05:23:31 +00:00
|
|
|
.Sh NAME
|
1996-04-17 20:50:44 +00:00
|
|
|
.Nm pstat ,
|
|
|
|
.Nm swapinfo
|
1994-05-26 05:23:31 +00:00
|
|
|
.Nd display system data structures
|
|
|
|
.Sh SYNOPSIS
|
2000-11-20 20:10:44 +00:00
|
|
|
.Nm
|
2007-04-03 08:16:06 +00:00
|
|
|
.Op Fl Tfghkmnst
|
2004-03-26 09:28:03 +00:00
|
|
|
.Op Fl M Ar core Op Fl N Ar system
|
1995-05-13 17:25:23 +00:00
|
|
|
.Nm swapinfo
|
2007-04-03 08:16:06 +00:00
|
|
|
.Op Fl ghkm
|
2004-03-26 09:28:03 +00:00
|
|
|
.Op Fl M Ar core Op Fl N Ar system
|
1994-05-26 05:23:31 +00:00
|
|
|
.Sh DESCRIPTION
|
2002-07-14 14:47:15 +00:00
|
|
|
The
|
|
|
|
.Nm
|
|
|
|
utility displays open file entry, swap space utilization,
|
1994-05-26 05:23:31 +00:00
|
|
|
terminal state, and vnode data structures.
|
1995-05-13 17:25:23 +00:00
|
|
|
.Pp
|
2001-06-03 16:08:25 +00:00
|
|
|
If invoked as
|
1995-05-13 17:25:23 +00:00
|
|
|
.Nm swapinfo
|
2001-06-03 16:08:25 +00:00
|
|
|
the
|
1995-05-13 17:25:23 +00:00
|
|
|
.Fl s
|
|
|
|
option is implied, and only the
|
2007-04-03 08:16:06 +00:00
|
|
|
.Fl k , m , g ,
|
2007-04-01 20:28:37 +00:00
|
|
|
and
|
|
|
|
.Fl h
|
|
|
|
options are legal.
|
1994-05-26 05:23:31 +00:00
|
|
|
.Pp
|
2004-03-26 09:28:03 +00:00
|
|
|
If the
|
2004-03-26 09:04:48 +00:00
|
|
|
.Fl M
|
2004-03-26 09:28:03 +00:00
|
|
|
option is not specified, information is obtained from
|
2004-03-26 09:04:48 +00:00
|
|
|
the currently running kernel via the
|
|
|
|
.Xr sysctl 3
|
|
|
|
interface.
|
|
|
|
Otherwise, information is read from the specified core file,
|
|
|
|
using the name list from the specified kernel image (or from
|
|
|
|
the default image).
|
|
|
|
.Pp
|
1997-10-09 07:22:08 +00:00
|
|
|
The following options are available:
|
1994-05-26 05:23:31 +00:00
|
|
|
.Bl -tag -width indent
|
1995-05-13 17:25:23 +00:00
|
|
|
.It Fl n
|
|
|
|
Print devices out by major/minor instead of name.
|
2005-03-21 16:36:05 +00:00
|
|
|
.It Fl h
|
|
|
|
.Dq Human-readable
|
|
|
|
output.
|
|
|
|
Use unit suffixes when printing swap partition sizes:
|
|
|
|
Byte, Kilobyte, Megabyte, Gigabyte, Terabyte and Petabyte.
|
1995-05-13 17:25:23 +00:00
|
|
|
.It Fl k
|
1999-11-27 17:03:07 +00:00
|
|
|
Print sizes in kilobytes, regardless of the setting of the
|
|
|
|
.Ev BLOCKSIZE
|
1995-05-13 17:25:23 +00:00
|
|
|
environment variable.
|
2007-04-01 20:28:37 +00:00
|
|
|
.It Fl m
|
|
|
|
Print sizes in megabytes, regardless of the setting of the
|
|
|
|
.Ev BLOCKSIZE
|
|
|
|
environment variable.
|
|
|
|
.It Fl g
|
|
|
|
Print sizes in gigabytes, regardless of the setting of the
|
|
|
|
.Ev BLOCKSIZE
|
|
|
|
environment variable.
|
1994-05-26 05:23:31 +00:00
|
|
|
.It Fl T
|
2001-06-03 16:08:25 +00:00
|
|
|
Print the number of used and free slots in several system tables.
|
|
|
|
This is useful for checking to see how large system tables have become
|
1994-05-26 05:23:31 +00:00
|
|
|
if the system is under heavy load.
|
|
|
|
.It Fl f
|
|
|
|
Print the open file table with these headings:
|
|
|
|
.Bl -tag -width indent
|
|
|
|
.It LOC
|
|
|
|
The core location of this table entry.
|
|
|
|
.It TYPE
|
|
|
|
The type of object the file table entry points to.
|
|
|
|
.It FLG
|
|
|
|
Miscellaneous state variables encoded thus:
|
2001-01-17 09:07:31 +00:00
|
|
|
.Pp
|
|
|
|
.Bl -tag -width indent -compact
|
1994-05-26 05:23:31 +00:00
|
|
|
.It R
|
|
|
|
open for reading
|
|
|
|
.It W
|
|
|
|
open for writing
|
|
|
|
.It A
|
|
|
|
open for appending
|
|
|
|
.It I
|
|
|
|
signal pgrp when data ready
|
|
|
|
.El
|
|
|
|
.It CNT
|
|
|
|
Number of processes that know this open file.
|
|
|
|
.It MSG
|
|
|
|
Number of messages outstanding for this file.
|
|
|
|
.It DATA
|
|
|
|
The location of the vnode table entry or socket structure for this file.
|
|
|
|
.It OFFSET
|
|
|
|
The file offset (see
|
|
|
|
.Xr lseek 2 ) .
|
|
|
|
.El
|
|
|
|
.It Fl s
|
2001-06-03 16:08:25 +00:00
|
|
|
Print information about swap space usage on all the
|
1994-05-26 05:23:31 +00:00
|
|
|
swap areas compiled into the kernel.
|
2004-07-02 23:13:00 +00:00
|
|
|
The first column is the device name of the partition.
|
|
|
|
The next column is
|
|
|
|
the total space available in the partition.
|
|
|
|
The
|
1994-05-26 05:23:31 +00:00
|
|
|
.Ar Used
|
2004-07-03 18:35:53 +00:00
|
|
|
column indicates the total blocks used so far; the
|
1994-05-26 05:23:31 +00:00
|
|
|
.Ar Available
|
|
|
|
column indicates how much space is remaining on each partition.
|
|
|
|
The
|
|
|
|
.Ar Capacity
|
|
|
|
reports the percentage of space used.
|
|
|
|
.Pp
|
|
|
|
If more than one partition is configured into the system, totals for all
|
|
|
|
of the statistics will be reported in the final line of the report.
|
|
|
|
.It Fl t
|
|
|
|
Print table for terminals
|
|
|
|
with these headings:
|
|
|
|
.Bl -tag -width indent
|
2004-11-11 17:30:04 +00:00
|
|
|
.It LINE
|
|
|
|
Device name.
|
Integrate the new MPSAFE TTY layer to the FreeBSD operating system.
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
2008-08-20 08:31:58 +00:00
|
|
|
.It INQ
|
|
|
|
Number of characters that can be stored in the input queue.
|
1994-05-26 05:23:31 +00:00
|
|
|
.It CAN
|
Integrate the new MPSAFE TTY layer to the FreeBSD operating system.
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
2008-08-20 08:31:58 +00:00
|
|
|
Number of characters in the input queue which can be read.
|
|
|
|
.It LIN
|
|
|
|
Number of characters in the input queue which cannot be read yet.
|
|
|
|
.It LOW
|
|
|
|
Low water mark for input.
|
|
|
|
.It OUTQ
|
|
|
|
Number of characters that can be stored in the output queue.
|
|
|
|
.It USE
|
|
|
|
Number of bytes in the output queue.
|
|
|
|
.It LOW
|
2008-08-20 22:09:33 +00:00
|
|
|
Low water mark for output.
|
1994-05-26 05:23:31 +00:00
|
|
|
.It COL
|
|
|
|
Calculated column position of terminal.
|
Integrate the new MPSAFE TTY layer to the FreeBSD operating system.
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
2008-08-20 08:31:58 +00:00
|
|
|
.It SESS
|
|
|
|
Kernel address of the session structure.
|
|
|
|
.It PGID
|
|
|
|
Process group for which this is the controlling terminal.
|
1994-05-26 05:23:31 +00:00
|
|
|
.It STATE
|
|
|
|
Miscellaneous state variables encoded thus:
|
2001-01-17 09:07:31 +00:00
|
|
|
.Pp
|
|
|
|
.Bl -tag -width indent -compact
|
Integrate the new MPSAFE TTY layer to the FreeBSD operating system.
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
2008-08-20 08:31:58 +00:00
|
|
|
.It I
|
|
|
|
init/lock-state device nodes present
|
1994-05-26 05:23:31 +00:00
|
|
|
.It C
|
Integrate the new MPSAFE TTY layer to the FreeBSD operating system.
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
2008-08-20 08:31:58 +00:00
|
|
|
callout device nodes present
|
|
|
|
.It O
|
|
|
|
opened
|
2009-02-05 14:21:09 +00:00
|
|
|
.It c
|
|
|
|
console in use
|
Integrate the new MPSAFE TTY layer to the FreeBSD operating system.
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
2008-08-20 08:31:58 +00:00
|
|
|
.It G
|
|
|
|
gone
|
1994-05-26 05:23:31 +00:00
|
|
|
.It B
|
Integrate the new MPSAFE TTY layer to the FreeBSD operating system.
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
2008-08-20 08:31:58 +00:00
|
|
|
busy in
|
|
|
|
.Xr open 2
|
1995-07-21 17:03:34 +00:00
|
|
|
.It Y
|
|
|
|
send SIGIO for input events
|
1995-10-06 20:58:24 +00:00
|
|
|
.It L
|
|
|
|
next character is literal
|
Integrate the new MPSAFE TTY layer to the FreeBSD operating system.
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
2008-08-20 08:31:58 +00:00
|
|
|
.It H
|
|
|
|
high watermark reached
|
|
|
|
.It X
|
|
|
|
open for exclusive use
|
|
|
|
.It S
|
|
|
|
output stopped (ixon flow control)
|
1995-07-21 17:03:34 +00:00
|
|
|
.It l
|
|
|
|
block mode input routine in use
|
|
|
|
.It Z
|
|
|
|
connection lost
|
2008-09-22 19:25:14 +00:00
|
|
|
.It s
|
|
|
|
i/o being snooped
|
2009-02-11 16:28:49 +00:00
|
|
|
.It b
|
|
|
|
busy in
|
|
|
|
.Xr read 2
|
|
|
|
or
|
|
|
|
.Xr write 2
|
1994-05-26 05:23:31 +00:00
|
|
|
.El
|
Integrate the new MPSAFE TTY layer to the FreeBSD operating system.
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
2008-08-20 08:31:58 +00:00
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Ql i
|
|
|
|
and
|
|
|
|
.Ql o
|
|
|
|
characters refer to the previous character, to differentiate between
|
|
|
|
input and output.
|
1994-05-26 05:23:31 +00:00
|
|
|
.El
|
2001-01-16 22:05:28 +00:00
|
|
|
.It Fl M
|
2004-03-26 09:04:48 +00:00
|
|
|
Extract values associated with the name list from the specified core.
|
2001-01-16 22:05:28 +00:00
|
|
|
.It Fl N
|
2004-03-26 09:28:03 +00:00
|
|
|
If
|
|
|
|
.Fl M
|
|
|
|
is also specified,
|
|
|
|
extract the name list from the specified system instead of the default,
|
2004-03-26 09:04:48 +00:00
|
|
|
which is the kernel image the system has booted from.
|
1994-05-26 05:23:31 +00:00
|
|
|
.El
|
|
|
|
.Sh SEE ALSO
|
|
|
|
.Xr ps 1 ,
|
|
|
|
.Xr systat 1 ,
|
|
|
|
.Xr stat 2 ,
|
|
|
|
.Xr fs 5 ,
|
1996-01-20 07:29:11 +00:00
|
|
|
.Xr iostat 8 ,
|
|
|
|
.Xr vmstat 8
|
1994-05-26 05:23:31 +00:00
|
|
|
.Rs
|
2000-12-27 15:30:30 +00:00
|
|
|
.%T UNIX Implementation
|
|
|
|
.%A K. Thompson
|
1994-05-26 05:23:31 +00:00
|
|
|
.Re
|
|
|
|
.Sh HISTORY
|
|
|
|
The
|
2000-11-20 20:10:44 +00:00
|
|
|
.Nm
|
2002-07-14 14:47:15 +00:00
|
|
|
utility appeared in
|
1996-08-23 20:36:11 +00:00
|
|
|
.Bx 4.0 .
|
2005-01-18 20:02:45 +00:00
|
|
|
.Sh BUGS
|
|
|
|
Does not understand
|
|
|
|
.Tn NFS
|
|
|
|
swap servers.
|