public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Morgenstein <jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: rolandd-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	diego-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org,
	eli-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org,
	Tziporet Koren <tziporet-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
Subject: [PATCH 0/4] XRC patch set
Date: Sun, 28 Feb 2010 11:02:07 +0200	[thread overview]
Message-ID: <201002281102.08286.jackm@dev.mellanox.co.il> (raw)

Hi Roland,
Sorry for the long delay -- I was out for a week with a stomach infection,
and was too weak to work.

Here is the XRC kernel patch set.  This patch set includes:
1. Your replacement/fix for your git's xrc-branch HEAD commit:
    "IB/uverbs: Support for associating XRC domains to inodes"
2. the XRC low-level (mlx4) driver XRC base implementation
3. The XRC_RCV implementation for the IB core and low-level (mlx4) driver.

We have done some testing of XRC and XRC_RCV with your xrc kernel git,
and this patch set applied on top of it (minus your HEAD, which the first patch of
this set replaces -- it is the same patch that you sent to me for review).

For userspace, we used the OFED 1.5.1 libmlx4 and libibverbs, which have XRC implemented 
in a fashion compatible with the kernel implementation in these patches.

Please note that, per Diego Cupernicoff's request, I have added a destroy_xrc_rcv_qp verb
to the kernel for users who do not wish to use the reg/unreg_xrc_rcv_qp() pair. The userspace
libraries I will be submitting (hopefully this week) will include this verb.

Hopefully, this patch set is sufficient for you to continue with RoCEE.

Best Regards,
-Jack

--
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

                 reply	other threads:[~2010-02-28  9:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201002281102.08286.jackm@dev.mellanox.co.il \
    --to=jackm-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=diego-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
    --cc=eli-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rolandd-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
    --cc=tziporet-VPRAkNaXOzVS1MOuV/RT9w@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