On Sun, Jul 29, 2007 at 05:04:31PM +0300, Michael S. Tsirkin wrote:
Hello!
Here is an API proposal for support of the SRC
(scalable reliable connected) protocol extension in libibverbs.
This adds APIs to:
- manage SRC domains
- share SRC domains between processes,
by means of creating
On Sun, Jul 29, 2007 at 05:04:31PM +0300, Michael S. Tsirkin wrote:
Hello!
Here is an API proposal for support of the SRC
(scalable reliable connected) protocol extension in libibverbs.
This adds APIs to:
- manage SRC domains
- share SRC domains between processes,
by means
On Mon, Jul 30, 2007 at 11:52:21AM +0300, Michael S. Tsirkin wrote:
On Sun, Jul 29, 2007 at 05:04:31PM +0300, Michael S. Tsirkin wrote:
Hello!
Here is an API proposal for support of the SRC
(scalable reliable connected) protocol extension in libibverbs.
This adds APIs to:
-
Some code examples:
/* create a domain and share it: */
struct ibv_src_domain * d = ibv_get_new_src_domain(ctx);
int fd = open(path, O_CREAT | O_RDWR, mode);
ibv_share_src_domain(d, fd);
/* get a reference to a shared domain: */
int fd =
On Mon, Jul 30, 2007 at 12:01:40PM +0300, Michael S. Tsirkin wrote:
Some code examples:
/* create a domain and share it: */
struct ibv_src_domain * d = ibv_get_new_src_domain(ctx);
int fd = open(path, O_CREAT | O_RDWR, mode);
ibv_share_src_domain(d, fd);
/*
More code examples:
Create an SRC QP, part of SRC domain:
attr.qp_type = IBV_QPT_SRC;
attr.src_domain = d;
qp = ibv_create_qp(pd, attr);
Given remote SRQ number, send data to this SRQ over an SRC QP:
wr.src_remote_srq_num = src_remote_srq_num;
On Mon, Jul 30, 2007 at 12:16:39PM +0300, Michael S. Tsirkin wrote:
More code examples:
Create an SRC QP, part of SRC domain:
attr.qp_type = IBV_QPT_SRC;
attr.src_domain = d;
qp = ibv_create_qp(pd, attr);
Given remote SRQ number, send data to this SRQ over an SRC QP:
Michael S. Tsirkin wrote:
Quoting Erez Zilber [EMAIL PROTECTED]:
Subject: Why isn't kfifo get built with ib-core for RH4?
Michael,
I saw that kfifo that was built with ib-core for RH4 was removed:
Quoting Gleb Natapov [EMAIL PROTECTED]:
Subject: Re: [ofa-general] RFC: SRC API
On Mon, Jul 30, 2007 at 12:16:39PM +0300, Michael S. Tsirkin wrote:
More code examples:
Create an SRC QP, part of SRC domain:
attr.qp_type = IBV_QPT_SRC;
attr.src_domain = d;
qp =
It seems what you are missing is what SRC is, not how to use the API.
So tell us.
This calls for a separate document. From feedback from Sonoma I really assumed
people have it figured out.
Let's open a separate thread, and there I will try writing up
what SRC is from the protocol point of
On Mon, Jul 30, 2007 at 03:10:57PM +0300, Michael S. Tsirkin wrote:
It seems what you are missing is what SRC is, not how to use the API.
So tell us.
This calls for a separate document. From feedback from Sonoma I really assumed
people have it figured out.
Let's open a separate
Arlin Davis wrote:
I would like to propose adding project directories under
http://www.openfabrics.org/downloads/ where appropriate and give
maintainers access. For example:
Jeff, please add the following directories with maintainer access as
follow (or grant access at a maintainer group
Here's some background on what SRC is. This is basically slide 6 in Dror's
talk, for those that missed the talk.
* * *
SRC is an extension supported by recent Mellanox hardware
which is geared toward reducing the number of QPs
required for all-to-all communication on systems
with a high
The following patches move open-iscsi crypto functions from kernel_patches to
kernel_addons. By doing so, we also solve a bug in iscsi tx hash that caused an
oops when crc32c was used for data digest.
Vlad - can you include this fix for OFED 1.2.1?
--
move open-iscsi crypto functions to kernel_addons (SLES10, RHEL5)
Signed-off-by: Erez Zilber [EMAIL PROTECTED]
---
.../backport/2.6.16_sles10/include/linux/crypto.h | 54
.../2.6.16_sles10_sp1/include/linux/crypto.h | 54
.../backport/2.6.18_FC6/include/linux/crypto.h |
move open-iscsi crypto functions to kernel_addons (RHEL4)
Signed-off-by: Erez Zilber [EMAIL PROTECTED]
---
.../backport/2.6.9_U3/include/linux/crypto.h | 55 ++--
.../backport/2.6.9_U4/include/linux/crypto.h | 55 ++--
.../backport/2.6.9_U5/include/linux/crypto.h
Michael S. Tsirkin wrote:
Quoting Erez Zilber [EMAIL PROTECTED]:
Subject: Why isn't kfifo get built with ib-core for RH4?
Michael,
I saw that kfifo that was built with ib-core for RH4 was removed:
The following patches add kfifo to ibcore (for SLES9 RH4). kfifo is taken
from upstream code.
Thanks, applied to 1.2.c and ofed_kernel.
Vlad already took 1.2.c, and will I guess take ofed_kernel
after it passes his checks.
--
MST
___
ewg mailing
Am I missing the call info? I tried an older conf id, and it didn't
work. Can you please post the conf call info along with the meeting
notification?
Thanks,
Steve.
Tziporet Koren wrote:
Hi All,
We will have our bi-weekly OFED meeting today at 9am PST
Agenda:
- Status update
- Bugzilla
Yes, you missed it; the call was over about half an hour ago. I [re-]
posted the dial-in info about 3 hours before the call this morning on
the ewg list.
On Jul 30, 2007, at 12:55 PM, Steve Wise wrote:
Am I missing the call info? I tried an older conf id, and it
didn't work. Can you
At 11:03 AM 7/30/2007, Jeff Squyres wrote:
Yes, you missed it; the call was over about half an hour ago. I
[re-] posted the dial-in info about 3 hours before the call this morning on
the ewg list.
I am on the EWG list and didn't see it. :-(
On Jul 30, 2007, at 12:55 PM, Steve Wise
[shrug] I sent it today at 8:21am US Eastern time:
http://lists.openfabrics.org/pipermail/ewg/2007-July/004075.html
Maybe check your spam folder?
On Jul 30, 2007, at 3:18 PM, Parks Fields wrote:
At 11:03 AM 7/30/2007, Jeff Squyres wrote:
Yes, you missed it; the call was over about
Jeff Squyres wrote:
Yes, you missed it; the call was over about half an hour ago. I
[re-]posted the dial-in info about 3 hours before the call this morning
on the ewg list.
I see. That's why I missed it. I'm not on the ewg list.
Are all attendees expected to be on the ewg list?
Steve.
On Jul 30, 2007, at 7:10 PM, Steve Wise wrote:
Yes, you missed it; the call was over about half an hour ago. I
[re-]posted the dial-in info about 3 hours before the call this
morning on the ewg list.
I see. That's why I missed it. I'm not on the ewg list.
Are all attendees expected to
24 matches
Mail list logo
