From mboxrd@z Thu Jan 1 00:00:00 1970 From: Flavio Leitner Subject: Re: [PATCH net-next] net: preserve sock reference when scrubbing the skb. Date: Tue, 26 Jun 2018 21:39:25 -0300 Message-ID: <20180627003925.GV19565@plex.lan> References: <20180625155610.30802-1-fbl@redhat.com> <48e15faf-f935-0166-e1db-18f7286e7264@gmail.com> <20180626220300.GT19565@plex.lan> <20180626233302.GU19565@plex.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Eric Dumazet , Linux Kernel Network Developers , Paolo Abeni , David Miller , Florian Westphal , NetFilter To: Cong Wang Return-path: Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-Id: netfilter-devel.vger.kernel.org On Tue, Jun 26, 2018 at 05:29:51PM -0700, Cong Wang wrote: > On Tue, Jun 26, 2018 at 4:33 PM Flavio Leitner wrote: > > > > It is still isolated, the sk carries the netns info and it is > > orphaned when it re-enters the stack. > > Then what difference does your patch make? Don't forget it is fixing two issues. > Before your patch: > veth orphans skb in its xmit > > After your patch: > RX orphans it when re-entering stack (as you claimed, I don't know) ip_rcv, and equivalents. > And for veth pair: > xmit from one side is RX for the other side > So, where is the queueing? Where is the buffer bloat? GRO list?? CPU backlog. -- Flavio