From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Why haven't NetMap or MegaPipe been merged?
Date: Mon, 12 Feb 2018 12:55:56 -0500 [thread overview]
Message-ID: <34904.1518458156@turing-police.cc.vt.edu> (raw)
In-Reply-To: <CAJEMUN8d9B4EMZdB4hakf=M3hsxvAbxarOSmZghCU3jukodZfw@mail.gmail.com>
On Mon, 12 Feb 2018 12:48:11 -0500, Demi Obenour said:
> Why haven't NetMap or MegaPipe been merged? I am wondering because they
> seem to be big wins for performance, but neither has been upstreamed.
It helps if you help identify things for those who haven't been deeply involved.
Are these IP network things, or fiberchannel stuff, or Infiniband, or something else?
Where is *mergeable* source for them? (usually, the "why isn't this already merged?"
is "because the code is a steaming pile of dingo's kidneys").
Are there actual measurements rather than just "seem to be big wins"?
What downsides are there? What configurations does this become a big performance *loss*?
Are the downsides documented?
And that's just the start of questions that will get asked before it gets merged....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20180212/bef91732/attachment.sig>
next prev parent reply other threads:[~2018-02-12 17:55 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 [this message]
2018-02-12 19:21 ` Greg KH
2018-02-13 18:00 ` Demi Obenour
2018-02-14 8:51 ` Greg KH
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=34904.1518458156@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--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).