From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Why haven't NetMap or MegaPipe been merged?
Date: Wed, 14 Feb 2018 09:51:04 +0100 [thread overview]
Message-ID: <20180214085104.GC11479@kroah.com> (raw)
In-Reply-To: <CAJEMUN-=MKyX7Ufpjm-NxKv8NLPmz4Vm48M9QPD+mjC2KfOFQA@mail.gmail.com>
On Tue, Feb 13, 2018 at 01:00:39PM -0500, Demi Obenour wrote:
> Not sure. The NetMap team at least told me that upstream didn't want their
> code. This might be because NetMap requires special vendor-provided (but
> still open source, if I understand correctly) drivers for optimum
> performance, or it might be because they use a single codebase to support
> Windows, Linux, and FreeBSD, if I understand correctly.
Well, "special" drivers, as well as a compatibility layer for other
operating systems are a very good reason to not get the code merged into
the kernel. No subsystem would ever accept such an odd requirement.
greg k-h
prev parent reply other threads:[~2018-02-14 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJEMUN-7PqmJEZymszE0rndVePS2CV_NCwHc3RsQG5y3R7HLTQ@mail.gmail.com>
[not found] ` <CAJEMUN-km774F6P-k2KHLEmQ8XKChL4xOzV9apWo+=e32G1V5A@mail.gmail.com>
2018-02-12 17:48 ` Why haven't NetMap or MegaPipe been merged? Demi Obenour
2018-02-12 17:55 ` valdis.kletnieks at vt.edu
2018-02-12 19:21 ` Greg KH
2018-02-13 18:00 ` Demi Obenour
2018-02-14 8:51 ` Greg KH [this message]
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=20180214085104.GC11479@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).