Searched refs:pf_retrans (Results 1 – 8 of 8) sorted by relevance
90 int pf_retrans; member
207 .data = &init_net.sctp.pf_retrans,220 .extra1 = &init_net.sctp.pf_retrans,
69 peer->pf_retrans = net->sctp.pf_retrans; in sctp_transport_init()
89 asoc->pf_retrans = sp->pf_retrans; in sctp_association_init()631 peer->pf_retrans = asoc->pf_retrans; in sctp_assoc_add_peer()
3875 trans->pf_retrans = val->spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3892 trans->pf_retrans = val->spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3899 asoc->pf_retrans = val->spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3907 sp->pf_retrans = val->spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()4880 sp->pf_retrans = net->sctp.pf_retrans; in sctp_init_sock()7042 val.spt_pathpfthld = trans->pf_retrans; in sctp_getsockopt_paddr_thresholds()7054 val.spt_pathpfthld = asoc->pf_retrans; in sctp_getsockopt_paddr_thresholds()7060 val.spt_pathpfthld = sp->pf_retrans; in sctp_getsockopt_paddr_thresholds()
548 transport->error_count > transport->pf_retrans) { in sctp_do_8_2_transport_strike()
187 __u16 pf_retrans; member893 __u16 pf_retrans; member1774 __u16 pf_retrans; member
2387 of pf_retrans > path_max_retrans also disables pf state. That is, one of2388 both pf_enable and pf_retrans > path_max_retrans can disable pf state.2389 Since pf_retrans and path_max_retrans can be changed by userspace2391 pf_retrans > path_max_retrans, but occasionally the value of pf_retrans2494 pf_retrans - INTEGER2498 passes the pf_retrans threshold can still be used. Its only2503 for details. Note also that a value of pf_retrans > path_max_retrans2504 disables this feature. Since both pf_retrans and path_max_retrans can2518 and its value can't be less than 'pf_retrans' when changing by sysctl.
