Re: tcp lro tso path mtu

2023-07-06 Thread Jan Klemkow
On Thu, Jul 06, 2023 at 10:19:21PM +0300, Alexander Bluhm wrote: > On Thu, Jul 06, 2023 at 08:49:03PM +0200, Jan Klemkow wrote: > > > @@ -109,6 +109,9 @@ > > > #include > > > #include > > > #include > > > > I think is a merge bug, isn't it? > > > > > +#include > > > +#include > > >

Re: tcp lro tso path mtu

2023-07-06 Thread Alexander Bluhm
On Thu, Jul 06, 2023 at 08:49:03PM +0200, Jan Klemkow wrote: > > @@ -109,6 +109,9 @@ > > #include > > #include > > #include > > I think is a merge bug, isn't it? > > > +#include > > +#include > > +#include Right. > > + error = tcp_if_output_tso(ifp, mp, dst, rt, ifcap, mtu); > > +

Re: tcp lro tso path mtu

2023-07-06 Thread Jan Klemkow
On Mon, Jul 03, 2023 at 08:04:11PM +0300, Alexander Bluhm wrote: > As final step before making LRO (Large Receive Offload) the default, > we have to fix path MTU discovery when forwarding. > > The drivers, currently ix(4) and lo(4) only, record an upper bound > of the size of the original packets

tcp lro tso path mtu

2023-07-03 Thread Alexander Bluhm
Hi, As final step before making LRO (Large Receive Offload) the default, we have to fix path MTU discovery when forwarding. The drivers, currently ix(4) and lo(4) only, record an upper bound of the size of the original packets in ph_mss. When sending we must chop the packets with TSO (TCP