Searched refs:pf_retrans (Results 1 – 8 of 8) sorted by relevance
90 int pf_retrans; member
69 peer->pf_retrans = net->sctp.pf_retrans; in sctp_transport_init()
88 asoc->pf_retrans = sp->pf_retrans; in sctp_association_init()626 peer->pf_retrans = asoc->pf_retrans; in sctp_assoc_add_peer()
210 .data = &init_net.sctp.pf_retrans,
3966 trans->pf_retrans = val.spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3981 trans->pf_retrans = val.spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3986 asoc->pf_retrans = val.spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3992 sp->pf_retrans = val.spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()5043 sp->pf_retrans = net->sctp.pf_retrans; in sctp_init_sock()7194 val.spt_pathpfthld = trans->pf_retrans; in sctp_getsockopt_paddr_thresholds()7205 val.spt_pathpfthld = asoc->pf_retrans; in sctp_getsockopt_paddr_thresholds()7210 val.spt_pathpfthld = sp->pf_retrans; in sctp_getsockopt_paddr_thresholds()
550 (transport->error_count > transport->pf_retrans)) { in sctp_do_8_2_transport_strike()
187 int pf_retrans; member899 int pf_retrans; member1775 int pf_retrans; member
2077 of pf_retrans > path_max_retrans also disables pf state. That is, one of2078 both pf_enable and pf_retrans > path_max_retrans can disable pf state.2079 Since pf_retrans and path_max_retrans can be changed by userspace2081 pf_retrans > path_max_retrans, but occasionally the value of pf_retrans2160 pf_retrans - INTEGER2164 passes the pf_retrans threshold can still be used. Its only2169 for details. Note also that a value of pf_retrans > path_max_retrans2170 disables this feature. Since both pf_retrans and path_max_retrans can
