From: Philip Frey <philip.frey-gy3b+zu4XSAfv37vnLkPlQ@public.gmane.org>
To: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org,
bmt-OA+xvbQnYDHMbYB6QlFGEg@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Simplified iWARP Consumer Library
Date: Sat, 6 Mar 2010 00:18:20 +0100 [thread overview]
Message-ID: <4B91913C.8000705@inf.ethz.ch> (raw)
In-Reply-To: <02600C74DFEE41EFAD9D387CF5A837CC-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
I'll have to look into that. So far, the library was intended as an add-on
to the existing code with the option to fall back to the original API if
need be.
Which of the features would you want to see in librdmacm? I guess the
integration of the cm_id and qp as well as the simpler (synchronous) connection
establishment and teardown functionality would fit. However, all cm events
will thereafter be handled within the library rather than being presented to the
user. Does that make sense?
Sean Hefty wrote:
>> as announced last week (on general-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org), I have developed a
>> shared library to simplify iWARP/RDMA application development on Linux in the
>> course of my PhD. The library, called libiwarp, is based on libibverbs and
>> librdmacm - it is essentially a set of wrappers to hide some of the complexity.
>
> I briefly toured through the code, and it seems to offer these main features:
>
> 1. Joins the rdma_cm_id and qp together into a single construct.
> 2. Supports synchronous rdma_cm operation.
> 3. Abstracts some initialization, like opening the device, creating PDs, etc.
> 4. Simplifies some verbs operations.
>
> Would it be possible to submit patches against the librdmacm to integrate some
> of these features?
>
> --
> 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
--
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
next prev parent reply other threads:[~2010-03-05 23:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 15:43 Simplified iWARP Consumer Library Philip Frey
[not found] ` <4B796BBD.5050007-gy3b+zu4XSAfv37vnLkPlQ@public.gmane.org>
2010-02-16 5:28 ` Or Gerlitz
[not found] ` <4B7A2CF8.1070002-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2010-02-16 7:28 ` Philip Frey
2010-03-05 23:06 ` Sean Hefty
[not found] ` <02600C74DFEE41EFAD9D387CF5A837CC-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-03-05 23:18 ` Philip Frey [this message]
[not found] ` <4B91913C.8000705-gy3b+zu4XSAfv37vnLkPlQ@public.gmane.org>
2010-03-06 0:07 ` Sean Hefty
[not found] ` <34C415061F244870BB8A526637CD04B0-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-03-11 22:49 ` Sean Hefty
-- strict thread matches above, loose matches on Subject: below --
2010-03-12 6:44 philip.frey-gy3b+zu4XSAfv37vnLkPlQ
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=4B91913C.8000705@inf.ethz.ch \
--to=philip.frey-gy3b+zu4xsafv37vnlkplq@public.gmane.org \
--cc=bmt-OA+xvbQnYDHMbYB6QlFGEg@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=phil-dElbnslWKco@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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