linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Richard Frank <richard.frank@oracle.com>
Cc: tziporet@dev.mellanox.co.il, linux-kernel@vger.kernel.org,
	general@lists.openfabrics.org
Subject: Re: [ofa-general] InfiniBand/iWARP/RDMA merge plans for 2.6.26 (what's in infiniband.git)
Date: Fri, 04 Apr 2008 12:34:52 -0700	[thread overview]
Message-ID: <adaiqyxs9b7.fsf@cisco.com> (raw)
In-Reply-To: <47F68EDC.4050107@oracle.com> (Richard Frank's message of "Fri, 04 Apr 2008 15:26:04 -0500")

 > We are very interested in these new operations and are moving in the
 > direction of tightly integrating RDMA along with atomics (if
 > available) into Oracle.  We plan on testing some early prototypes of
 > the these in the few months.

And you need the ConnectX-only masked atomics?  Or do the standard IB
atomic operations work for you?  Of course using atomics at all means
that things don't work on iWARP.

 > Send with invalidate is an exact match for our current RDS V3 rdma
 > driver - and should be more efficient than the current background
 > syncing of the tpt  to ensure keys are invalidated.

How does send with invalidate interact with the current IB FMR stuff?
Seems that you would run into trouble keeping the state of the FMR
straight if the remote side is invalidating them.

Also I would think that send-with-invalidate would be much more
expensive than the current FMR method of batching up the invalidates,
since you don't get to amortize the cost of syncing up all the internal
HCA state.

 - R.

  reply	other threads:[~2008-04-04 19:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 20:02 InfiniBand/iWARP/RDMA merge plans for 2.6.26 (what's in infiniband.git) Roland Dreier
2008-04-01 16:55 ` [ofa-general] " Shirley Ma
2008-04-02  7:22 ` Shirley Ma
2008-04-02 15:27   ` Roland Dreier
2008-04-02 17:11     ` Richard Frank
2008-04-02 16:15       ` Roland Dreier
2008-04-02 17:18         ` Richard Frank
2008-04-02 16:26           ` Roland Dreier
2008-04-02 17:28             ` Richard Frank
2008-04-02 17:24         ` Richard Frank
2008-04-02 16:29           ` [ofa-general] InfiniBand/iWARP/RDMA merge plans for 2.6.26 (what'sin infiniband.git) Scott Weitzenkamp (sweitzen)
2008-04-02 17:37             ` Richard Frank
2008-04-02 16:46               ` Scott Weitzenkamp (sweitzen)
2008-04-02 18:00                 ` Richard Frank
2008-04-02 17:04                   ` Scott Weitzenkamp (sweitzen)
2008-04-02 12:31 ` [ofa-general] InfiniBand/iWARP/RDMA merge plans for 2.6.26 (what's in infiniband.git) Tziporet Koren
2008-04-02 16:19   ` Roland Dreier
2008-04-03 11:40     ` Tziporet Koren
2008-04-04 20:26     ` Richard Frank
2008-04-04 19:34       ` Roland Dreier [this message]
2008-04-04 22:21         ` Richard Frank
2008-04-04  5:54   ` Or Gerlitz
     [not found] <OF1D776305.7E25BAA6-ON8725741F.005B027C-8825741F.002F5161@us.ibm.com>
2008-04-02 16:37 ` Roland Dreier

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=adaiqyxs9b7.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=general@lists.openfabrics.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.frank@oracle.com \
    --cc=tziporet@dev.mellanox.co.il \
    /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).