From: Amir Vadai <amirv@mellanox.co.il>
To: Steve Wise <swise@opengridcomputing.com>,
Andrea Gozzelino <Andrea.Gozzelino@lnl.infn.it>
Cc: "Tung, Chien Tin" <chien.tin.tung@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"rolandd@cisco.com" <rolandd@cisco.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"pavel@ucw.cz" <pavel@ucw.cz>, "mingo@elte.hu" <mingo@elte.hu>,
Eric B Munson <ebmunson@us.ibm.com>
Subject: Re: Socket Direct Protocol: help (2)
Date: Wed, 14 Apr 2010 18:03:57 +0300 [thread overview]
Message-ID: <4BC5D95D.3010108@mellanox.co.il> (raw)
In-Reply-To: <4BC5D727.4090400@opengridcomputing.com>
You are right - I missed it.
Andrea, Please open a bug at bugzilla (https://bugs.openfabrics.org) -
so that you will be notified as soon as I will fix SDP not use FMR if
not supported.
As to fastreg_mrs support - I don't know this mechanism. Do you mean FRWR?
Thanks,
Amir
On 04/14/2010 05:54 PM, Steve Wise wrote:
> Hey Amir,
>
> I don't think this helps because sdp_add_device() will not add rdma
> devices that fail to create fmr pools.
>
> So I guess you could key off of fmr pool failures and set
> sdp_zcopy_thresh to 0 and allow the device to be used?
>
> But what we really need is sdp support for fastreg_mrs as an
> alternative to fmrs.
>
>
> Steve.
>
>
> Amir Vadai wrote:
>
>> Hi,
>>
>> FMR are being used only in a special mode called ZCopy.
>>
>> You could disable this mode by setting the module paramter
>> sdp_zcopy_thresh to 0, or by issuing:
>> # echo 0 > /sys/module/ib_sdp/parameters/sdp_zcopy_thresh
>>
>> This means that you won't get the benefits of Zero-copy.
>>
>> - Amir
>>
>> On 04/14/2010 11:51 AM, Andrea Gozzelino wrote:
>>
>>
>>> On Apr 13, 2010 10:22 PM, "Tung, Chien Tin" <chien.tin.tung@intel.com>
>>> wrote:
>>>
>>>
>>>
>>>
>>>>>>> Chien, does the NE020 support FMRs? I looked at the nes ofed-1.5
>>>>>>> code
>>>>>>> and it appears to do nothing in the map_phys_fmr functions.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> We never implemented map_phys_fmr. Is it relevant to the # of SGEs?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> No, but SDP uses FMRs. I don't think it will run without FMR support.
>>>>>
>>>>>
>>>>>
>>>>>
>>>> Good to know. Thanks.
>>>>
>>>> Chien
>>>>
>>>>
>>>>
>>>>
>>>>
>>> Hi Steve and Chien,
>>>
>>> I understand that NE020 cards have problem with SDP connected with
>>> map_phy_fmr (FMR stands for Fast Memory Region).
>>> Is it possible to solve/fix this point?
>>> If yes, have you an idea about the time that is necessary to code
>>> development/build?
>>> If no, can you suggest me a card that supports SDP protocol?
>>>
>>> I work on NE020 cards from February 2010 for an INFN experimental
>>> proposal, called REDIGO (Read out at 10 Gbits/s), about the data
>>> acquisition and movement systems. The covergence of storage protocols
>>> around 10 Gigabits/s Ethernet protocols shows that one way could be the
>>> Remote Direct Memory Access (RDMA). The goals are the investigations of
>>> latency time, the throughput, the buffer size schemes and finally the
>>> global event building bandwidth.
>>>
>>> Do you know if NE020 cards have problems with librdma (RDMA procedures,
>>> in general) and / or with MPI versions?
>>>
>>> Thank you very much,
>>> Andrea
>>>
>>> Andrea Gozzelino
>>>
>>> INFN - Laboratori Nazionali di Legnaro (LNL)
>>> Viale dell'Universita' 2
>>> I-35020 - Legnaro (PD)- ITALIA
>>> Tel: +39 049 8068346
>>> Fax: +39 049 641925
>>> Mail: andrea.gozzelino@lnl.infn.it
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>>
>>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>>
>
>
next prev parent reply other threads:[~2010-04-14 15:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13381_1271060138_o3C8FUH8013968_2977669.1271060085255.SLOX.WebMail.wwwrun@imap.lnl.infn.it>
2010-04-12 14:33 ` Andrea Gozzelino
2010-04-13 16:28 ` Tung, Chien Tin
2010-04-13 16:39 ` Steve Wise
2010-04-13 20:02 ` Tung, Chien Tin
2010-04-13 20:20 ` Steve Wise
2010-04-13 20:22 ` Tung, Chien Tin
2010-04-14 8:51 ` Andrea Gozzelino
2010-04-14 14:31 ` Amir Vadai
2010-04-14 14:46 ` Amir Vadai
2010-04-14 15:01 ` Tung, Chien Tin
2010-04-14 15:05 ` Steve Wise
2010-04-14 15:14 ` Andrea Gozzelino
2010-04-14 18:48 ` Tung, Chien Tin
2010-04-15 6:24 ` Amir Vadai
2010-04-15 7:07 ` Andrea Gozzelino
2010-04-15 8:38 ` Amir Vadai
2010-04-20 13:53 ` Andrea Gozzelino
2010-04-21 12:01 ` Amir Vadai
2010-04-23 14:34 ` SDP bugs 2027 and 2028 Andrea Gozzelino
2010-04-25 7:35 ` Amir Vadai
2010-04-23 14:35 ` Andrea Gozzelino
2010-04-23 14:35 ` Socket Direct Protocol: help (2) Andrea Gozzelino
2010-04-14 14:54 ` Steve Wise
2010-04-14 15:03 ` Amir Vadai [this message]
2010-04-14 15:08 ` Steve Wise
2010-04-14 15:16 ` Amir Vadai
2010-04-14 19:24 ` Tung, Chien Tin
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=4BC5D95D.3010108@mellanox.co.il \
--to=amirv@mellanox.co.il \
--cc=Andrea.Gozzelino@lnl.infn.it \
--cc=chien.tin.tung@intel.com \
--cc=ebmunson@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rolandd@cisco.com \
--cc=swise@opengridcomputing.com \
/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
Powered by JetHome