Searched refs:pf_retrans (Results 1 – 8 of 8) sorted by relevance
90 int pf_retrans; member
84 peer->pf_retrans = net->sctp.pf_retrans; in sctp_transport_init()
104 asoc->pf_retrans = net->sctp.pf_retrans; in sctp_association_init()645 peer->pf_retrans = asoc->pf_retrans; in sctp_assoc_add_peer()
228 .data = &init_net.sctp.pf_retrans,
564 (asoc->pf_retrans < transport->pathmaxrxt) && in sctp_do_8_2_transport_strike()565 (transport->error_count > asoc->pf_retrans)) { in sctp_do_8_2_transport_strike()
3904 trans->pf_retrans = val.spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3909 asoc->pf_retrans = val.spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3918 trans->pf_retrans = val.spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()6879 val.spt_pathpfthld = asoc->pf_retrans; in sctp_getsockopt_paddr_thresholds()6888 val.spt_pathpfthld = trans->pf_retrans; in sctp_getsockopt_paddr_thresholds()
909 int pf_retrans; member1777 int pf_retrans; member
1954 of pf_retrans > path_max_retrans also disables pf state. That is, one of1955 both pf_enable and pf_retrans > path_max_retrans can disable pf state.1956 Since pf_retrans and path_max_retrans can be changed by userspace1958 pf_retrans > path_max_retrans, but occasionally the value of pf_retrans2037 pf_retrans - INTEGER2041 passes the pf_retrans threshold can still be used. Its only2046 for details. Note also that a value of pf_retrans > path_max_retrans2047 disables this feature. Since both pf_retrans and path_max_retrans can
