From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexei Starovoitov Subject: Re: [PATCH v4 net-next 2/2] tc: add 'needs_l2' flag to ingress qdisc Date: Fri, 10 Apr 2015 18:39:06 -0700 Message-ID: <55287B3A.50103@plumgrid.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "David S. Miller" , Eric Dumazet , Daniel Borkmann , Thomas Graf , Jiri Pirko , Jamal Hadi Salim , netdev To: Cong Wang Return-path: Received: from mail-pa0-f54.google.com ([209.85.220.54]:33713 "EHLO mail-pa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751967AbbDKBjI (ORCPT ); Fri, 10 Apr 2015 21:39:08 -0400 Received: by paboj16 with SMTP id oj16so38213863pab.0 for ; Fri, 10 Apr 2015 18:39:08 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On 4/10/15 5:45 PM, Cong Wang wrote: > > The problem you try to solve is kernel's implementation problem, > users should not care, so we should make some effort to make ingress > align with egress, rather than making more differences. Agree. I already tried to do this unconditionally in v2. Folks have raised concerns that it may break some tc modules and in general doesn't work for all types of netdevs that don't set headers_ops. So this flag is the safe compromise. Personally I will be always turning it on.