summaryrefslogtreecommitdiffstats
path: root/release
diff options
context:
space:
mode:
authorrwatson <rwatson@FreeBSD.org>2004-06-14 18:16:22 +0000
committerrwatson <rwatson@FreeBSD.org>2004-06-14 18:16:22 +0000
commitf2c0db1521299639d6b16b7d477a777fbd81ada6 (patch)
tree38ab74987dd7d2d27fad4ea4e4772c7d36baf7d4 /release
parent1598e7b4234febacb1b16af62169c90a2e93cc6b (diff)
downloadFreeBSD-src-f2c0db1521299639d6b16b7d477a777fbd81ada6.zip
FreeBSD-src-f2c0db1521299639d6b16b7d477a777fbd81ada6.tar.gz
The socket field so_state is used to hold a variety of socket related
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.
Diffstat (limited to 'release')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud