diff options
| author | David S. Miller <[email protected]> | 2019-01-30 00:44:08 -0800 | 
|---|---|---|
| committer | David S. Miller <[email protected]> | 2019-01-30 00:44:08 -0800 | 
| commit | 804a15cdbbc3834504e161ee461c67f8eea959a4 (patch) | |
| tree | 294679d5e9274ec31c22f9b1fd4be29279fecafb /tools/perf/scripts/python | |
| parent | bde52726430755a25e1c28e26e7fa4a7967d4680 (diff) | |
| parent | 7efba10d6bd22030fb5931e50bf97496f932f00e (diff) | |
Merge branch 'sctp-support-SCTP_FUTURE-CURRENT-ALL_ASSOC'
Xin Long says:
====================
sctp: support SCTP_FUTURE/CURRENT/ALL_ASSOC
This patchset adds the support for 3 assoc_id constants: SCTP_FUTURE_ASSOC
SCTP_CURRENT_ASSOC, SCTP_ALL_ASSOC, described in rfc6458#section-7.2:
   All socket options set on a one-to-one style listening socket also
   apply to all future accepted sockets.  For one-to-many style sockets,
   often a socket option will pass a structure that includes an assoc_id
   field.  This field can be filled with the association identifier of a
   particular association and unless otherwise specified can be filled
   with one of the following constants:
   SCTP_FUTURE_ASSOC:  Specifies that only future associations created
      after this socket option will be affected by this call.
   SCTP_CURRENT_ASSOC:  Specifies that only currently existing
      associations will be affected by this call, and future
      associations will still receive the previous default value.
   SCTP_ALL_ASSOC:  Specifies that all current and future associations
      will be affected by this call.
The functions for many other sockopts that use assoc_id also need to be
updated accordingly.
====================
Acked-by: Neil Horman <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions