From: Roland Dreier <rdreier@cisco.com>
To: tziporet@dev.mellanox.co.il
Cc: linux-kernel@vger.kernel.org, general@lists.openfabrics.org,
linux-rdma@vger.kernel.org
Subject: Re: [ofa-general] InfiniBand/RDMA merge plans for 2.6.32
Date: Thu, 03 Sep 2009 10:40:55 -0700 [thread overview]
Message-ID: <ada4orkoriw.fsf@cisco.com> (raw)
In-Reply-To: <4A9FB004.6020904@mellanox.co.il> (Tziporet Koren's message of "Thu, 03 Sep 2009 15:01:08 +0300")
> What about RDMAoE?
> Patches were sent few weeks ago and it seems you ignore them.
Sorry, I should have mentioned that.
Yes, I have been ignoring the patches -- I want to get through XRC
first, and also I would like to see a real spec for IBoE (that resolves
issues like multicast interaction with IGMP, address resolution, etc) so
we can judge whether the current patches match the long-term direction
or are just a point-in-time hack.
- R.
next prev parent reply other threads:[~2009-09-03 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 23:12 InfiniBand/RDMA merge plans for 2.6.32 Roland Dreier
2009-09-03 12:01 ` [ofa-general] " Tziporet Koren
2009-09-03 17:40 ` Roland Dreier [this message]
2009-09-06 15:06 ` Tziporet Koren
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=ada4orkoriw.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--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