diff options
Diffstat (limited to 'Documentation/networking')
-rw-r--r-- | Documentation/networking/rxrpc.txt | 62 |
1 files changed, 62 insertions, 0 deletions
diff --git a/Documentation/networking/rxrpc.txt b/Documentation/networking/rxrpc.txt index b89bc82eed46..aa08d2625f05 100644 --- a/Documentation/networking/rxrpc.txt +++ b/Documentation/networking/rxrpc.txt | |||
@@ -27,6 +27,8 @@ Contents of this document: | |||
27 | 27 | ||
28 | (*) AF_RXRPC kernel interface. | 28 | (*) AF_RXRPC kernel interface. |
29 | 29 | ||
30 | (*) Configurable parameters. | ||
31 | |||
30 | 32 | ||
31 | ======== | 33 | ======== |
32 | OVERVIEW | 34 | OVERVIEW |
@@ -864,3 +866,63 @@ The kernel interface functions are as follows: | |||
864 | 866 | ||
865 | This is used to allocate a null RxRPC key that can be used to indicate | 867 | This is used to allocate a null RxRPC key that can be used to indicate |
866 | anonymous security for a particular domain. | 868 | anonymous security for a particular domain. |
869 | |||
870 | |||
871 | ======================= | ||
872 | CONFIGURABLE PARAMETERS | ||
873 | ======================= | ||
874 | |||
875 | The RxRPC protocol driver has a number of configurable parameters that can be | ||
876 | adjusted through sysctls in /proc/net/rxrpc/: | ||
877 | |||
878 | (*) req_ack_delay | ||
879 | |||
880 | The amount of time in milliseconds after receiving a packet with the | ||
881 | request-ack flag set before we honour the flag and actually send the | ||
882 | requested ack. | ||
883 | |||
884 | Usually the other side won't stop sending packets until the advertised | ||
885 | reception window is full (to a maximum of 255 packets), so delaying the | ||
886 | ACK permits several packets to be ACK'd in one go. | ||
887 | |||
888 | (*) soft_ack_delay | ||
889 | |||
890 | The amount of time in milliseconds after receiving a new packet before we | ||
891 | generate a soft-ACK to tell the sender that it doesn't need to resend. | ||
892 | |||
893 | (*) idle_ack_delay | ||
894 | |||
895 | The amount of time in milliseconds after all the packets currently in the | ||
896 | received queue have been consumed before we generate a hard-ACK to tell | ||
897 | the sender it can free its buffers, assuming no other reason occurs that | ||
898 | we would send an ACK. | ||
899 | |||
900 | (*) resend_timeout | ||
901 | |||
902 | The amount of time in milliseconds after transmitting a packet before we | ||
903 | transmit it again, assuming no ACK is received from the receiver telling | ||
904 | us they got it. | ||
905 | |||
906 | (*) max_call_lifetime | ||
907 | |||
908 | The maximum amount of time in seconds that a call may be in progress | ||
909 | before we preemptively kill it. | ||
910 | |||
911 | (*) dead_call_expiry | ||
912 | |||
913 | The amount of time in seconds before we remove a dead call from the call | ||
914 | list. Dead calls are kept around for a little while for the purpose of | ||
915 | repeating ACK and ABORT packets. | ||
916 | |||
917 | (*) connection_expiry | ||
918 | |||
919 | The amount of time in seconds after a connection was last used before we | ||
920 | remove it from the connection list. Whilst a connection is in existence, | ||
921 | it serves as a placeholder for negotiated security; when it is deleted, | ||
922 | the security must be renegotiated. | ||
923 | |||
924 | (*) transport_expiry | ||
925 | |||
926 | The amount of time in seconds after a transport was last used before we | ||
927 | remove it from the transport list. Whilst a transport is in existence, it | ||
928 | serves to anchor the peer data and keeps the connection ID counter. | ||