Searched refs:pf_retrans (Results 1 – 8 of 8) sorted by relevance
104 int pf_retrans; member
118 .data = &init_net.sctp.pf_retrans,131 .extra1 = &init_net.sctp.pf_retrans,613 table[SCTP_PS_RETRANS_IDX].extra1 = &net->sctp.pf_retrans; in sctp_sysctl_net_register()
89 asoc->pf_retrans = sp->pf_retrans; in sctp_association_init()634 peer->pf_retrans = asoc->pf_retrans; in sctp_assoc_add_peer()
69 peer->pf_retrans = net->sctp.pf_retrans; in sctp_transport_init()
3888 trans->pf_retrans = val->spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3905 trans->pf_retrans = val->spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3912 asoc->pf_retrans = val->spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3920 sp->pf_retrans = val->spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()5010 sp->pf_retrans = net->sctp.pf_retrans; in sctp_init_sock()7174 val.spt_pathpfthld = trans->pf_retrans; in sctp_getsockopt_paddr_thresholds()7186 val.spt_pathpfthld = asoc->pf_retrans; in sctp_getsockopt_paddr_thresholds()7192 val.spt_pathpfthld = sp->pf_retrans; in sctp_getsockopt_paddr_thresholds()
584 transport->error_count > transport->pf_retrans) { in sctp_do_8_2_transport_strike()
191 __u16 pf_retrans; member903 __u16 pf_retrans; member1794 __u16 pf_retrans; member
2796 of pf_retrans > path_max_retrans also disables pf state. That is, one of2797 both pf_enable and pf_retrans > path_max_retrans can disable pf state.2798 Since pf_retrans and path_max_retrans can be changed by userspace2800 pf_retrans > path_max_retrans, but occasionally the value of pf_retrans2903 pf_retrans - INTEGER2907 passes the pf_retrans threshold can still be used. Its only2912 for details. Note also that a value of pf_retrans > path_max_retrans2913 disables this feature. Since both pf_retrans and path_max_retrans can2927 and its value can't be less than 'pf_retrans' when changing by sysctl.
Completed in 33 milliseconds