From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Bernard Metzler <BMT-OA+xvbQnYDHMbYB6QlFGEg@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Software iWARP stack
Date: Sun, 14 Mar 2010 11:34:30 -0700 [thread overview]
Message-ID: <adaiq8yah1l.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <OF64DD5621.D563EA15-ONC12576E6.00510BE1-C12576E6.005B5E57-Xeyd2O9EBijQT0dZR+AlfA@public.gmane.org> (Bernard Metzler's message of "Sun, 14 Mar 2010 17:37:59 +0100")
> We at IBM Zurich Laboratory are developing a full-software
> iWARP stack to run within the OpenFabrics verbs framework.
> Today we open sourced that work to be available at
> http://gitorious.org/softiwarp. It consists of a kernel
> module (siw) and a user level library (libsiw).
Great, congratulations on finally releasing this.
I will take a look at this, and I hope we can move this towards the
mainline kernel. With the current backlog of things to review/merge,
unfortunately I don't think 2.6.35 is realistic; so let's set a goal of
getting this into 2.6.36.
One thing you could do that would make this a little easier to test and
review would be to have the kernel driver tree be based on the main
kernel -- ie a git tree based on Linus's kernel tree with exactly the
patches required to add softiwarp support committed. It may seem crazy
to carry the full kernel tree with your relatively small amount of code,
but git makes this really cheap (I can clone your tree with "--reference
<my-main-kernel-tree>" and only get one copy of all the objects in
common), and it makes it much easier to build and test.
Also I would suggest posting your announcement to netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
too, to get review comments from the networking guys. If you can split
your code up into a digestible series of patches for review by email,
that would help too (post to both netdev@ and linux-rmda@). Having the
git tree is useful for following development, testing, building etc, and
having the patches by email is useful for reading and reviewing the
code -- it makes sending comments back much easier.
- Roland
--
Roland Dreier <rolandd-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
--
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:[~2010-03-14 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 16:37 Software iWARP stack Bernard Metzler
[not found] ` <OF64DD5621.D563EA15-ONC12576E6.00510BE1-C12576E6.005B5E57-Xeyd2O9EBijQT0dZR+AlfA@public.gmane.org>
2010-03-14 18:34 ` Roland Dreier [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=adaiq8yah1l.fsf@roland-alpha.cisco.com \
--to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
--cc=BMT-OA+xvbQnYDHMbYB6QlFGEg@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