Re: [PATCH net-next 1/2] tcp: uniform the set up of sockets after successful connection

2017-10-03 Thread Wei Wang
On Tue, Oct 3, 2017 at 9:28 PM, David Miller wrote: > From: Wei Wang > Date: Mon, 2 Oct 2017 10:01:35 -0700 > >> @@ -456,6 +456,19 @@ void tcp_init_sock(struct sock *sk) >> } >> EXPORT_SYMBOL(tcp_init_sock); >> >> +void tcp_init_transfer(struct sock *sk, int bpf_op) >> +{ >> + struct inet_

Re: [PATCH net-next 1/2] tcp: uniform the set up of sockets after successful connection

2017-10-03 Thread David Miller
From: Wei Wang Date: Mon, 2 Oct 2017 10:01:35 -0700 > @@ -456,6 +456,19 @@ void tcp_init_sock(struct sock *sk) > } > EXPORT_SYMBOL(tcp_init_sock); > > +void tcp_init_transfer(struct sock *sk, int bpf_op) > +{ > + struct inet_connection_sock *icsk = inet_csk(sk); > + > + tcp_mtup_init

[PATCH net-next 1/2] tcp: uniform the set up of sockets after successful connection

2017-10-02 Thread Wei Wang
From: Wei Wang Currently in the TCP code, the initialization sequence for cached metrics, congestion control, BPF, etc, after successful connection is very inconsistent. This introduces inconsistent bevhavior and is prone to bugs. The current call sequence is as follows: (1) for active case (tcp