Searched refs:pf_retrans (Results 1 – 8 of 8) sorted by relevance
89 int pf_retrans; member
84 peer->pf_retrans = net->sctp.pf_retrans; in sctp_transport_init()
105 asoc->pf_retrans = net->sctp.pf_retrans; in sctp_association_init()624 peer->pf_retrans = asoc->pf_retrans; in sctp_assoc_add_peer()
228 .data = &init_net.sctp.pf_retrans,
507 (asoc->pf_retrans < transport->pathmaxrxt) && in sctp_do_8_2_transport_strike()508 (transport->error_count > asoc->pf_retrans)) { in sctp_do_8_2_transport_strike()
3614 trans->pf_retrans = val.spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3619 asoc->pf_retrans = val.spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()3628 trans->pf_retrans = val.spt_pathpfthld; in sctp_setsockopt_paddr_thresholds()5829 val.spt_pathpfthld = asoc->pf_retrans; in sctp_getsockopt_paddr_thresholds()5838 val.spt_pathpfthld = trans->pf_retrans; in sctp_getsockopt_paddr_thresholds()
867 int pf_retrans; member1565 int pf_retrans; member
1792 pf_retrans - INTEGER1796 passes the pf_retrans threshold can still be used. Its only1801 for details. Note also that a value of pf_retrans > path_max_retrans