From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: Focusing the XDP project Date: Tue, 21 Feb 2017 13:11:00 -0500 (EST) Message-ID: <20170221.131100.165451416977377136.davem@davemloft.net> References: <20170221.114617.1686255511436946338.davem@davemloft.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: saeedm@mellanox.com, alexander.duyck@gmail.com, brouer@redhat.com, alexei.starovoitov@gmail.com, john.fastabend@gmail.com, netdev@vger.kernel.org, bblanco@gmail.com To: tom@herbertland.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:55858 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752751AbdBUSLH (ORCPT ); Tue, 21 Feb 2017 13:11:07 -0500 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Tom Herbert Date: Tue, 21 Feb 2017 09:40:17 -0800 > I'd be more supportive of this line of thinking if we (e.g. FB) didn't > have to spend the majority time over the past few months trying to > deal with all the complexity being thrown into drivers for all these > new features such as XDP. Case in point, Mellanox drivers are > completely non-modular and have a horrible directory structure. They > tried to fix, this but the patch set was rejected because it would > break people trying to do backports. That's a fair argument, but the > lesson I gather from that is that we should put more time in up front > thinking about how to structure code the right way instead of just > throwing it in and trying to deal with the consequences later. Hey aren't you guys suffering from this because you're stuck on an older kernel for one reason or another? Don't we constantly give the Android guys a hard time about this? ;-)