From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Christoph Hellwig' <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: New krping location
Date: Tue, 9 Aug 2016 08:47:25 -0500 [thread overview]
Message-ID: <006701d1f244$8f99e320$aecda960$@opengridcomputing.com> (raw)
In-Reply-To: <20160809072024.GA10141-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
>
> Is there any good reason why we don't have a version of krping in
> the kernel tree?
The current code needs refactoring to be acceptable in the kernel. For example,
it abuses procfs as the interface to control krping connections from user space.
There are hacked up latency and bandwidth tests that need to be fixed up or
removed (they current don't work at all). There have been comments that the
code flow needs to be cleaned up. So currently it is just a bare-bones test
tool.
I welcome anyone who wants to take on the task of pushing this into the kernel.
I know there are a few folks out there using it for rdma driver bring up...
Steve.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-08-09 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 19:40 New krping location Steve Wise
2016-08-09 7:20 ` Christoph Hellwig
[not found] ` <20160809072024.GA10141-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-08-09 13:47 ` Steve Wise [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='006701d1f244$8f99e320$aecda960$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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