From: David Miller <davem@davemloft.net>
To: tom@herbertland.com
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
Subject: Re: Focusing the XDP project
Date: Tue, 21 Feb 2017 13:11:00 -0500 (EST) [thread overview]
Message-ID: <20170221.131100.165451416977377136.davem@davemloft.net> (raw)
In-Reply-To: <CALx6S36qPxUgvmp4taQFd0OzWyQ9Z4Rv8t+cnph_MAQHiGkvCw@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
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? ;-)
next prev parent reply other threads:[~2017-02-21 18:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 10:13 Focusing the XDP project Jesper Dangaard Brouer
2017-02-20 20:09 ` Alexander Duyck
2017-02-20 22:57 ` Saeed Mahameed
2017-02-20 23:40 ` Alexander Duyck
2017-02-21 23:08 ` Saeed Mahameed
2017-02-21 16:35 ` Tom Herbert
2017-02-21 16:46 ` David Miller
2017-02-21 17:40 ` Tom Herbert
2017-02-21 18:11 ` David Miller [this message]
2017-02-21 18:23 ` Tom Herbert
2017-02-21 22:40 ` Saeed Mahameed
2017-02-21 23:04 ` Tom Herbert
2017-02-21 22:29 ` Saeed Mahameed
2017-02-21 22:54 ` Tom Herbert
2017-02-22 9:43 ` Jesper Dangaard Brouer
2017-02-22 17:22 ` Tom Herbert
2017-02-22 21:43 ` Jesper Dangaard Brouer
2017-02-22 22:08 ` Tom Herbert
2017-02-20 23:39 ` Jesper Dangaard Brouer
2017-02-21 0:39 ` Alexander Duyck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170221.131100.165451416977377136.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.duyck@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bblanco@gmail.com \
--cc=brouer@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=tom@herbertland.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).