Any further comments on this?
Doug -- does it look ok to you?
> On Dec 7, 2015, at 5:27 AM, Haggai Eran <hagg...@mellanox.com> wrote:
>
> On 12/04/2015 01:09 AM, Jeff Squyres wrote:
>> The default value of 8 is too small to read
>> /sys/class/infiniband/usnic_x/n
al BSD/GPL-licensed.
Signed-off-by: Jeff Squyres <jsquy...@cisco.com>
---
drivers/infiniband/hw/usnic/usnic.h | 21 ++---
drivers/infiniband/hw/usnic/usnic_abi.h | 21 ++---
drivers/infiniband/hw/usnic/usnic_common
this patch get into upstream distro libibverbs
releases. Once that happens, we can start planning the end of the horrible
hackarounds we had to put into place (e.g., in Open MPI) to suppress the
misleading libibverbs output.
Thanks!
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information
Ping.
This is just a periodic query to see if there has been any progress on
accepting this patch into libibverbs.
On Jun 3, 2015, at 12:50 PM, Doug Ledford dledf...@redhat.com wrote:
On Mon, 2015-06-01 at 22:02 +, Jeff Squyres (jsquyres) wrote:
On May 22, 2015, at 9:44 AM, Doug
.
This is just a periodic query to see if there has been any progress on
accepting this patch into libibverbs.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe
ofed 406548 May 5 2014 libibverbs-1.1.8.tar.gz
-rw-r--r--. 1 dledford ofed 384656 Apr 24 2007 libibverbs-1.1.tar.gz
-rw-r--r-- 1 dledford ofed 3957 May 7 2014 README.html
-rw-r--r--. 1 dledford ofed 60 Mar 12 2008 WEB_README
-
--
Jeff Squyres
jsquy...@cisco.com
For corporate
On May 9, 2015, at 8:04 AM, Yann Droneaud ydrone...@opteya.com wrote:
Le vendredi 08 mai 2015 à 11:21 -0700, Jeff Squyres a écrit :
Signed-off-by: Jeff Squyres jsquy...@cisco.com
This is a little short for an explanation: what was the issue with the
error messages ?
Cisco has stopped
Signed-off-by: Jeff Squyres jsquy...@cisco.com
---
src/init.c | 14 --
1 file changed, 14 deletions(-)
diff --git a/src/init.c b/src/init.c
index d0e4b1c..9c21768 100644
--- a/src/init.c
+++ b/src/init.c
@@ -557,19 +557,5 @@ HIDDEN int ibverbs_init(struct ibv_device ***list
Bump. This is V2 of the patch, which removes the ABI issue: libibverbs
directly calls the command in the kernel (without going through the provider
plugin).
On Aug 21, 2013, at 5:22 PM, Jeff Squyres jsquy...@cisco.com wrote:
Per lengthy discussion on the linux-rdma list, add a new verb
uv_cmd_query_port_max_datagram().
Signed-off-by: Jeff Squyres jsquy...@cisco.com
---
Makefile.am | 3 +-
examples/devinfo.c | 7 +
include/infiniband/driver.h | 4 +++
include/infiniband/kern-abi.h| 17 +++-
include/infiniband/verbs.h | 6
man
send the corresponding
kernel patch.
Signed-off-by: Jeff Squyres jsquy...@cisco.com
---
Makefile.am | 3 +-
examples/devinfo.c | 7 +
include/infiniband/driver.h | 4 +++
include/infiniband/kern-abi.h| 19 +++--
include/infiniband/verbs.h
(vs. a
struct lookup)
If the community likes this approach, I'll send the corresponding
kernel patch.
Signed-off-by: Jeff Squyres jsquy...@cisco.com
---
Makefile.am | 3 +-
examples/devinfo.c | 7 +
include/infiniband/driver.h | 4 +++
include
, the only failure for this call should be due to a bad port
number..
Sure, can do.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body
version to 7, no?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo info
is not supported. In that case, you can handle things like Jason
suggested.
Gotcha. I'll adjust the patch.
Any other feedback?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send
4th bump...
On Jul 10, 2013, at 4:32 PM, Jeff Squyres jsquy...@cisco.com wrote:
If the send size is less than the cap.max_inline_data reported by the
qp, use the IBV_SEND_INLINE flag. This now only shows the example of
using ibv_query_qp(), it also reduces the latency time shown
On Jul 23, 2013, at 9:26 AM, Jeff Squyres (jsquyres) jsquy...@cisco.com wrote:
.. and UD is the least abstracted transport, so existing apps won't
support Jeff's new NIC anyhow, MTU is the least of their problems.
Existing apps with existing transports see the same old values.
Bump
the prior posts on this thread
that describes the MTU issue and why we still need a solution.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma
Bump bump bump.
I know this isn't a huge / important patch, but it is a small thing that does
decrease the latency reported by these example programs.
On Jul 10, 2013, at 4:32 PM, Jeff Squyres jsquy...@cisco.com wrote:
If the send size is less than the cap.max_inline_data reported by the
qp
anyhow, MTU is the least of their problems.
Existing apps with existing transports see the same old values.
...so how do we move forward?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from
Bump bump.
On Jul 10, 2013, at 4:32 PM, Jeff Squyres jsquy...@cisco.com wrote:
If the send size is less than the cap.max_inline_data reported by the
qp, use the IBV_SEND_INLINE flag. This now only shows the example of
using ibv_query_qp(), it also reduces the latency time shown
wrong, but it doesn't matter much.
We need it for UD for our upcoming device, however, because the MTU is the only
way to get the max message size.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe
to believe the Doug/Jason position:
- MTU really needs to be a plain integer (not an enum)
- forcing application source change/adaptation is the safest way to move forward
- doing it this way preserves ABI, so existing binaries are safe
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal
Bump.
On Jul 10, 2013, at 8:14 AM, Jeff Squyres (jsquyres) jsquy...@cisco.com wrote:
On Jul 8, 2013, at 1:26 PM, Jason Gunthorpe jguntho...@obsidianresearch.com
wrote:
Jeff's patch doesn't break old binaries, old binaries, running with
normal IB MTUs work fine. The structure layouts all
Bump.
On Jul 10, 2013, at 4:32 PM, Jeff Squyres jsquy...@cisco.com wrote:
If the send size is less than the cap.max_inline_data reported by the
qp, use the IBV_SEND_INLINE flag. This now only shows the example of
using ibv_query_qp(), it also reduces the latency time shown by the
pingpong
-
Still works fine.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
N�r��yb�X��ǧv�^�){.n�+{��ٚ�{ay� ʇڙ�,j��f���h���z� �w���
���j:+v���w�j�mzZ+�ݢj��!�i
If the send size is less than the cap.max_inline_data reported by the
qp, use the IBV_SEND_INLINE flag. This now only shows the example of
using ibv_query_qp(), it also reduces the latency time shown by the
pingpong programs when the sends can be inlined.
Signed-off-by: Jeff Squyres jsquy
code and ABI changes, which
resulted in this patch.
I personally don't care which way this goes; I just want the ability to have
non-enum MTU values.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri
Bump.
On Jul 2, 2013, at 8:31 AM, Jeff Squyres jsquy...@cisco.com wrote:
(Previous patch did not include updates for the man pages)
Keep IBV_MTU_* enums values as they are, but pass MTU values around as
a struct containing a single int.
Per lengthy discusson on the linux-rdma list
to use the struct. Newer applications are
encouraged to use arbitrary int values, not the MTU enums (e.g., 1024,
1500, 9000).
(if people like the idea of this patch, I will send the corresponding
kernel patch)
Signed-off-by: Jeff Squyres jsquy...@cisco.com
---
Makefile.am| 3
is
touched. This is trivially done by wrapping it in a struct:
struct ibv_mtu_t {int __mtu;};
Sure, I can work up a patch that does this.
Do others agree? Roland?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal
because it is in the spirit of the other
enum-to-int/int-to-enum function pair naming conventions:
int ibv_rate_to_mult(enum ibv_rate rate);
enum ibv_rate mult_to_ibv_rate(int mult);
int ibv_rate_to_mbps(enum ibv_rate rate);
enum ibv_rate mbps_to_ibv_rate(int mbps);
--
Jeff Squyres
jsquy...@cisco.com
of this patch, I will send the corresponding
kernel patch)
Signed-off-by: Jeff Squyres jsquy...@cisco.com
---
Makefile.am| 3 ++-
examples/devinfo.c | 20 +++---
examples/pingpong.c| 12 -
examples/pingpong.h| 1 -
examples/rc_pingpong.c
respectively.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
is single-threaded), not in the library
itself.
But regardless, this whole function went away in V2 of the patch.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line
of this patch, I will send the corresponding
kernel patch)
Signed-off-by: Jeff Squyres jsquy...@cisco.com
---
examples/devinfo.c | 11 +--
examples/pingpong.c| 12
examples/pingpong.h| 1 -
examples/rc_pingpong.c | 8
examples
is that the
*application provides the buffer*, not MPI.
Hence, we're stuck with what buffers the user passes in.
This is the root of the whole MPI has a registration cache issue.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business
as memory pools. But given that userspace doesn't
control its virtual address ranges, I'm not sure how that's useful.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line
developers.
A practical example of using this would be to avoid the need to send
scatter buffer pointers to the remote. The remote writes into a memory
ring and the ring is made 'endless' by clever use of remapping.
I don't understand -- please explain your example a bit more...?
--
Jeff
management
(ummunotify, ODP, or something else), a non-blocking verb for registering
memory would still be a Very Useful Thing.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send
On Jun 6, 2013, at 4:33 PM, Jeff Squyres (jsquyres) jsquy...@cisco.com wrote:
I don't think this covers other memory regions, like those added via mmap,
right?
We talked about this at the MPI Forum this week; it doesn't seem like ODP fixes
any MPI problems.
1. MPI still has to have
, ...);
...
}
MPI_Send(buffer, ...) {
if (mpi_sbrk_save != sbrk())
mpi_sbrk_save = sbrk();
ibv_rereg_mr(..., 0, mpi_sbrk_save, ...);
...
}
I don't think this covers other memory regions, like those added via mmap,
right?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go
-blocking memory registration yet?
...etc.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
drawback is that this will break ABI; applications will
need to be recompiled.
(if this approach/patch is acceptable, I will submit a corresponding
patch for the kernel side)
Signed-off-by: Jeff Squyres jsquy...@cisco.com
---
examples/devinfo.c | 18 +-
examples/pingpong.c
)). But without that, unless I'm
missing something, I don't think it solves the MPI-must-catch-free-sbrk-etc.
issues...? And therefore, having some kind of ummunotify-like functionality as
a verb would be a Very Good Thing.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http
this go to a libibverbs 2.0, where it would be palatable to have an ABI
break?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body
return that.
- Make a ibv_from/to_mtu inline function to translate from bytes to
the encoded MTU value.
- Switch ibv_mtu from a enum to a typedef int ibv_mtu
That also breaks ABI, doesn't it?
Jason
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com
.
I started this thread asking the status of that branch.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord
just always returning 3. 3 is guarenteed compatible with all
users.
Old users will test directly against 3.
New users will call ibv_from_mtu which tests against 3 as well.
Ok.
I'll take a to-do to work up a new patch -- probably not until next week.
--
Jeff Squyres
jsquy...@cisco.com
provide any
details about what still needs to be done, though. :-)
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message
in mind that all RDMA access protections will be disabled if
you register the entire process VM, the remote(s) can scribble/read
everything..
No problem for MPI/HPC... :-)
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business
.
Is this correct?
He was very concerned about what the size of the TLB on the HCA, and therefore
what the actual run-time behavior would be for sending around large messages
via MPI -- i.e., would RDMA'ing 1GB messages now incur this
HCA-must-reload-its-TLB-and-therefore-incur-RNR-NAKs behavior?
--
Jeff
now incur this
HCA-must-reload-its-TLB-and-therefore-incur-RNR-NAKs behavior?
We have a mechanism to prefetch the pages needed for a large message
upon the first page fault, which can also help amortizing the cost of
the page fault for larger messages.
Ok, thanks.
--
Jeff Squyres
jsquy
register the entire
memory space (i.e., NULL to 2^64) and then never worry about registered memory?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux
community universally hated it.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More
community?
The limitation of a max of 2 concurrent page faults seems fairly significant.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma
need to be done at this point)
Has anything been done on the userspace side?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body
have no control over that. :-)
On Apr 25, 2013, at 11:38 AM, Jeff Squyres (jsquyres) jsquy...@cisco.com
wrote:
Bump.
On Apr 22, 2013, at 1:41 PM, Jeff Squyres jsquy...@cisco.com wrote:
The old sequence of Autotools commands listed in autogen.sh is no
longer correct. Instead, just use
, too.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
Bump bump. :-)
On Apr 25, 2013, at 11:38 AM, Jeff Squyres (jsquyres) jsquy...@cisco.com
wrote:
Bump.
On Apr 22, 2013, at 1:41 PM, Jeff Squyres jsquy...@cisco.com wrote:
The old sequence of Autotools commands listed in autogen.sh is no
longer correct. Instead, just use the single
Bump.
On Apr 22, 2013, at 1:41 PM, Jeff Squyres jsquy...@cisco.com wrote:
The old sequence of Autotools commands listed in autogen.sh is no
longer correct. Instead, just use the single autoreconf command,
which will invoke all the Right Autotools commands in the correct
order.
Signed-off
On Apr 19, 2013, at 8:19 PM, Hefty, Sean sean.he...@intel.com wrote:
It may help if you identify the library this patch is against. :)
3rd time sending will be the charm... :-)
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about
versions of Autoconf).
Signed-off-by: Jeff Squyres jsquy...@cisco.com
---
.gitignore | 6 +
configure.ac | 74
configure.in | 74
3 files changed, 80 insertions(+), 74
The old sequence of Autotools commands listed in autogen.sh is no
longer correct. Instead, just use the single autoreconf command,
which will invoke all the Right Autotools commands in the correct
order.
Signed-off-by: Jeff Squyres jsquy...@cisco.com
---
autogen.sh | 6 +-
1 file changed, 1
libibverbs to 2.x, and then intentionally change the MTU field names in
ibv_port_attr and ibv_qp_attr so that apps using those fields will fail to
compile with libibverbs 2.x (and therefore forcibly realize they need to adapt
to the new int MTU values)
--
Jeff Squyres
jsquy...@cisco.com
On Apr 12, 2013, at 11:40 AM, Jeff Squyres (jsquyres) jsquy...@cisco.com
wrote:
As an aside I like the use of RDMA_MTU_* for these values. Again to
distinguish them from the IBTA values. But I know that is poor form.
So what's the right way to move forward on this? Is it this:
enum
Bump.
Any thoughts on these two patches? They're pretty trivial, enable use with
modern versions of Autotools, and now feature the proper Signed-off-by line.
On Apr 13, 2013, at 8:15 AM, Jeff Squyres jsquy...@cisco.com wrote:
The old sequence of Autotools commands listed in autogen.sh
The old sequence of Autotools commands listed in autogen.sh is no
longer correct. Instead, just use the single autoreconf command,
which will invoke all the Right Autotools commands in the correct
order.
Signed-off-by: Jeff Squyres jsquy...@cisco.com
---
autogen.sh | 6 +-
1 file changed, 1
versions of Autoconf).
Signed-off-by: Jeff Squyres jsquy...@cisco.com
---
.gitignore | 6 +
configure.ac | 74
configure.in | 74
3 files changed, 80 insertions(+), 74
{
IB_MTU_256 = 1,
IB_MTU_512 = 2,
IB_MTU_1024 = 3,
IB_MTU_2048 = 4,
IB_MTU_4096 = 5,
RDMA_MTU_1500 = 1500,
RDMA_MTU_9000 = 9000
};
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal
,
RDMA_MTU_9000 = 9000
};
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo info
separately on that thread.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo
message size without knowing the actual MTU (are we incorrect
about that?). Hence, using the IB-defined values is not really sufficient.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from
Roland --
If there are no objections, can this patch (and patch 4 of this set:
https://patchwork.kernel.org/patch/2387321/) be committed? Neither should not
have any real impact other than the modernization of the libibverbs build
system.
On Apr 3, 2013, at 9:06 AM, Jeff Squyres jsquy
.
On Apr 4, 2013, at 5:27 PM, Or Gerlitz or.gerl...@gmail.com wrote:
Jeff Squyres (jsquyres) jsquy...@cisco.com wrote:
Sure. For a little background, the 2nd-generation Cisco VIC has been
available
since last year (IIRC): http://www.cisco.com/en/US/products/ps10277
Per my previous email, forgive my top reply...
RDMA_NODE_VENDOR would be great, actually. Should I work up a patch for that?
Sent from my phone. No type good.
On Apr 4, 2013, at 10:32 AM, Hefty, Sean sean.he...@intel.com wrote:
The reason we're asking for these IBV_*_USNIC enums now --
before we can submit good patches for these. The main driving factor for
submitting these new enums is so that they can be included in RHEL 6.5.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe
modernization of the GNU Autotools usage in libibverbs.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord
The old sequence of Autotools commands listed in autogen.sh is no
longer correct. Instead, just use the single autoreconf command,
which will invoke all the Right Autotools commands in the correct
order.
---
autogen.sh | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git
Per off-list conversation with Roland, add some new enums for the
Cisco Ethernet Virtual NIC (it's not an RNIC/iWARP device, so it
doesn't fit in the same category as RDMA_NODE_RNIC / RDMA_TRANSPORT_IWARP).
USNIC = Userspace NIC.
---
examples/devinfo.c | 1 +
include/infiniband/verbs.h
Allow specification of common Ethernet MTUs.
---
examples/devinfo.c | 2 ++
examples/pingpong.c| 2 ++
include/infiniband/verbs.h | 6 --
3 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/examples/devinfo.c b/examples/devinfo.c
index 98a6b4b..6700882 100644
---
Added some entries to config/.gitignore for newer versions of the GNU
Autotools. Also renamed configure.in - configure.ac to accomodate
newer GNU Autotools
(http://lists.gnu.org/archive/html/autotools-announce/2012-11/msg0.html
announced the intent to drop support for configure.in in future
Allow specification of common Ethernet MTUs.
---
include/rdma/ib_addr.h | 6 +-
include/rdma/ib_verbs.h | 8 ++--
2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/include/rdma/ib_addr.h b/include/rdma/ib_addr.h
index 9996539..1f6fbbc 100644
--- a/include/rdma/ib_addr.h
Per off-list conversation with Roland, add some new enums for the
Cisco Ethernet Virtual NIC (it's not an RNIC/iWARP device, so it
doesn't fit in the same category as RDMA_NODE_RNIC / RDMA_TRANSPORT_IWARP).
USNIC = Userspace NIC.
---
drivers/infiniband/core/verbs.c | 3 +++
crashes and does not properly deallocate the XRC
domain / tgt qp?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message
On Jul 21, 2011, at 8:47 AM, Jack Morgenstein wrote:
[snip]
When the last user of an XRC domain exits cleanly (or crashes), the domain
should be destroyed.
In this case, with Sean's design, the tgt qp's for the XRC domain should also
be destroyed.
Sounds perfect.
--
Jeff Squyres
jsquy
ever used XRC
You are correct, mvapich does not use XRC.
openMPI uses XRC, so hopefully you can use openMPI to test out your XRC stuff.
You can contact Jeff Squyres for details/help.
In the meantime, I include the following from the ewg list
processes in the application to be
terminated by signals sent by mpirun (as reported here).
--
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business
{
+ UMMUNOTIFY_EVENT_FLAG_HINT = 1 0,
+};
+
+struct ummunotify_event {
+ __u32 type;
+ __u32 flags;
+ __u64 hint_start;
+ __u64 hint_end;
+ __u64 user_cookie_counter;
+};
+
+#endif /* _LINUX_UMMUNOTIFY_H */
--
1.6.3.3
--
Jeff Squyres
jsquy...@cisco.com
things alone make doing something like ummunotify worthwhile, IMHO.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message
?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
to indicate how
many items in my_list were actually filled? Or is that the return value?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma
mechanisms to get the counter info (for example):
1. the above uverb
2. mmap
Right?
I don't really have an opinion here -- I'm not really an owner of the ibv
API. As long as there is a fast/mmap way for me to get the counter without an
extra function call, I'm happy. :-)
--
Jeff Squyres
jsquy
/mailman/listinfo/ewg
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo info
commit to remove 127.0.0.1 support for 2.6.33.
Steve.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord
to say that if a source address is given then
the rdma_cm_id will be bound to a device.
Which device is bound to if you specify 127.0.0.1 as the source address?
(which is what OMPI is doing) Is it possible to assign 127.0.0.1 to an RDMA
device?
--
Jeff Squyres
jsquy...@cisco.com
was saying that he saw it
rdma_bind_addr() succeeding on his machines with OFED 1.5.1rcwhatever (I don't
recall the OS he said he was using).
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from
= rdma_translate_ip(addr, id-route.addr.dev_addr);
if (ret)
goto err1;
I'll see if reverting this gives the desired(?) behavior.
Thanks!
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business
that you are
definitely using the OpenFabrics verbs support and forcing the use of RDMA CM.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ring_c.c
Description: Binary data
.
Can you clarify what kernel versions allow binding LOOPBACK addresses with RDMA
CM?
--
Jeff Squyres jsquy...@cisco.com
Cisco.com - http://www.cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To unsubscribe from this list: send
1 - 100 of 110 matches
Mail list logo
