Searched refs:pf_retrans (Results 1 – 8 of 8) sorted by relevance
101 int pf_retrans; member
212 .data = &init_net.sctp.pf_retrans,225 .extra1 = &init_net.sctp.pf_retrans,
89 asoc->pf_retrans = sp->pf_retrans; in sctp_association_init()637 peer->pf_retrans = asoc->pf_retrans; in sctp_assoc_add_peer()
69 peer->pf_retrans = net->sctp.pf_retrans; in sctp_transport_init()
3890 trans->pf_retrans = val->spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3907 trans->pf_retrans = val->spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3914 asoc->pf_retrans = val->spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3922 sp->pf_retrans = val->spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()5012 sp->pf_retrans = net->sctp.pf_retrans; in sctp_init_sock()7177 val.spt_pathpfthld = trans->pf_retrans; in sctp_getsockopt_paddr_thresholds()7189 val.spt_pathpfthld = asoc->pf_retrans; in sctp_getsockopt_paddr_thresholds()7195 val.spt_pathpfthld = sp->pf_retrans; in sctp_getsockopt_paddr_thresholds()
580 transport->error_count > transport->pf_retrans) { in sctp_do_8_2_transport_strike()
191 __u16 pf_retrans; member902 __u16 pf_retrans; member1791 __u16 pf_retrans; member
2575 of pf_retrans > path_max_retrans also disables pf state. That is, one of2576 both pf_enable and pf_retrans > path_max_retrans can disable pf state.2577 Since pf_retrans and path_max_retrans can be changed by userspace2579 pf_retrans > path_max_retrans, but occasionally the value of pf_retrans2682 pf_retrans - INTEGER2686 passes the pf_retrans threshold can still be used. Its only2691 for details. Note also that a value of pf_retrans > path_max_retrans2692 disables this feature. Since both pf_retrans and path_max_retrans can2706 and its value can't be less than 'pf_retrans' when changing by sysctl.
Completed in 59 milliseconds