Title: RE: [openib-general] MTHCA features
We recommend to work with FMRs and not memory windows due to performance.
FMRS are much faster and available for kernel modules only.
They are not yet implemented in mthca but it is possible to add them.
Tziporet
-Original Message-
From
NFS/RDMA doesn't require memory windows but it will make use of
them if they are available.
-james
On Tue, 1 Mar 2005, Roland Dreier wrote:
James> I ask because the DAT API contains interfaces that allow
James> users to interact with memory windows.
Are there any real applications that use
Or> By "performance characteristics" do you mean the extra
Or> overhead to generate another rkey for the already registered
Or> address range (and also to create/free the mw)?
No, I mean the performance cost of binding/unbinding the MW.
- R.
__
James> I ask because the DAT API contains interfaces that allow
James> users to interact with memory windows.
Are there any real applications that use those interfaces?
Thanks,
Roland
___
openib-general mailing list
openib-general@openib.org
h
roland> James> It is my understanding that the current MTHCA driver does
roland> James> not support InfiniBand memory windows or memory
roland> James> registration using virtual addresses.
roland>
roland> James> Is this information correct? If so, when will these
roland> James
Roland > Memory windows are not implemented for mthca. It wouldn't be a lot of
Roland > work for someone with access to Mellanox documentation to implement
Roland > them, but they're not particularly useful due to their performance
characteristics.
By "performance characteristics" do you mean th
James> It is my understanding that the current MTHCA driver does
James> not support InfiniBand memory windows or memory
James> registration using virtual addresses.
James> Is this information correct? If so, when will these
James> features be supported?
Well, memory registrati
