src-test2/sys/netinet/accf_http.c, branch release/6.2.0_cvsFreeBSD source treehttps://cgit-dev.freebsd.org/src-test2/atom?h=release%2F6.2.0_cvs2007-01-11T22:54:46ZThis commit was manufactured by cvs2svn to create tag2007-01-11T22:54:46Zcvs2svncvs2svn@FreeBSD.org2007-01-11T22:54:46Zurn:sha1:201f78d6b90635d961fa373ecd706e3786333b7e
'RELENG_6_2_0_RELEASE'.
This commit was manufactured to restore the state of the 6.2-RELEASE image.
/* -> /*- for license, minor formatting changes2005-01-07T01:45:51ZWarner Loshimp@FreeBSD.org2005-01-07T01:45:51Zurn:sha1:c398230b64aea809cb7c5cea8db580af7097920cThe socket field so_state is used to hold a variety of socket related2004-06-14T18:16:22ZRobert Watsonrwatson@FreeBSD.org2004-06-14T18:16:22Zurn:sha1:c0b99ffa021c0be74d6ab90a6eccfe511be8bb19
flags relating to several aspects of socket functionality. This change
breaks out several bits relating to send and receive operation into a
new per-socket buffer field, sb_state, in order to facilitate locking.
This is required because, in order to provide more granular locking of
sockets, different state fields have different locking properties. The
following fields are moved to sb_state:
SS_CANTRCVMORE (so_state)
SS_CANTSENDMORE (so_state)
SS_RCVATMARK (so_state)
Rename respectively to:
SBS_CANTRCVMORE (so_rcv.sb_state)
SBS_CANTSENDMORE (so_snd.sb_state)
SBS_RCVATMARK (so_rcv.sb_state)
This facilitates locking by isolating fields to be located with other
identically locked fields, and permits greater granularity in socket
locking by avoiding storing fields with different locking semantics in
the same short (avoiding locking conflicts). In the future, we may
wish to coallesce sb_state and sb_flags; for the time being I leave
them separate and there is no additional memory overhead due to the
packing/alignment of shorts in the socket buffer structure.
add missing #include <sys/module.h>2004-05-30T20:27:19ZPoul-Henning Kampphk@FreeBSD.org2004-05-30T20:27:19Zurn:sha1:5dba30f15ae1cec2dcdc19be3f3efa0331755f42Remove so*_locked(), which were backed out by mistake.2002-06-18T07:42:02ZSeigo Tanimuratanimura@FreeBSD.org2002-06-18T07:42:02Zurn:sha1:03e4918190e22ff4002e360efda68eb1882d11daBack out my lats commit of locking down a socket, it conflicts with hsu's work.2002-05-31T11:52:35ZSeigo Tanimuratanimura@FreeBSD.org2002-05-31T11:52:35Zurn:sha1:4cc20ab1f0f3d1126126327aa298ab88c974c53d
Requested by: hsu
Lock down a socket, milestone 1.2002-05-20T05:41:09ZSeigo Tanimuratanimura@FreeBSD.org2002-05-20T05:41:09Zurn:sha1:243917fe3b5e36464ab72473e872da9acd44aa1c
o Add a mutex (sb_mtx) to struct sockbuf. This protects the data in a
socket buffer. The mutex in the receive buffer also protects the data
in struct socket.
o Determine the lock strategy for each members in struct socket.
o Lock down the following members:
- so_count
- so_options
- so_linger
- so_state
o Remove *_locked() socket APIs. Make the following socket APIs
touching the members above now require a locked socket:
- sodisconnect()
- soisconnected()
- soisconnecting()
- soisdisconnected()
- soisdisconnecting()
- sofree()
- soref()
- sorele()
- sorwakeup()
- sotryfree()
- sowakeup()
- sowwakeup()
Reviewed by: alfred
Redo the sigio locking.2002-05-01T20:44:46ZAlfred Perlsteinalfred@FreeBSD.org2002-05-01T20:44:46Zurn:sha1:f132072368c112104e35151ee7a1c30a1b74a107
Turn the sigio sx into a mutex.
Sigio lock is really only needed to protect interrupts from dereferencing
the sigio pointer in an object when the sigio itself is being destroyed.
In order to do this in the most unintrusive manner change pgsigio's
sigio * argument into a **, that way we can lock internally to the
function.
Fix some edge cases where bad string handling could occur.2002-05-01T08:29:41ZAlfred Perlsteinalfred@FreeBSD.org2002-05-01T08:29:41Zurn:sha1:59017610b27fb3ecb43a9fd2811c1c368723a8f4
Submitted by: ps
cleanup:2002-05-01T08:08:24ZAlfred Perlsteinalfred@FreeBSD.org2002-05-01T08:08:24Zurn:sha1:ef1047305e7a53c59abbd8a1aba1234e8474b0d1
fix line wraps, add some comments, fix macro definitions, fix for(;;) loops.