Title: RE: [openib-general] segmentation fault in ibv_modify_srq
SRQ limit event will be supported also on cards with memory (both Infinihost and Infinihost III)
If someone need it nowadays we can give a drop of FW that supports it.
It will be officially released in Q4.
Tziporet
Roland,
* On Oct,13 Roland Dreier[EMAIL PROTECTED] wrote :
Sayantan I noticed that the test re-posts buffers only when the
Sayantan outstanding recv count is = 1. I set a SRQ limit as
Sayantan max_recv - 5. So, I should get the event when 5 WQEs are
Sayantan consumed from the
Sayantan,
The Limit Event must be re-armed after an event has occurred (it is a
one-shot).
(i.e., modify-srq/set-limit must be re-invoked).This is compliant with the
IB Spec (see section 10.2.9.3, first paragraph). (Note that after each SRQ LWM
event, the limit for the SRQ gets reset back to
Jack,
* On Oct,16 Jack Morgenstein[EMAIL PROTECTED] wrote :
Sayantan,
The Limit Event must be re-armed after an event has occurred (it is a
one-shot).
(i.e., modify-srq/set-limit must be re-invoked).This is compliant with the
IB Spec (see section 10.2.9.3, first paragraph). (Note that
* On Oct,10 Roland Dreier[EMAIL PROTECTED] wrote :
Sayantan I am getting a segmentation fault after a couple of
Sayantan thousand messages are sent over SRQ (using ping-pong
Sayantan latency test). Here is a snippet from the core
Sayantan generated.
Is it possible that you
Roland,
* On Oct,11 Sayantan Sur[EMAIL PROTECTED] wrote :
I will test out the limit event generation next.
I made some simple modifications to srq_pingpong.c to see if I am able
to generate the IBV_EVENT_SRQ_LIMIT_REACHED event. I have attached my
changes as a patch and the full file (for easy
Sayantan I noticed that the test re-posts buffers only when the
Sayantan outstanding recv count is = 1. I set a SRQ limit as
Sayantan max_recv - 5. So, I should get the event when 5 WQEs are
Sayantan consumed from the SRQ, right?
Yes, your code is correct. The problem was that
Roland,
* On Oct,13 Roland Dreier[EMAIL PROTECTED] wrote :
Sayantan I noticed that the test re-posts buffers only when the
Sayantan outstanding recv count is = 1. I set a SRQ limit as
Sayantan max_recv - 5. So, I should get the event when 5 WQEs are
Sayantan consumed from the
Sayantan Hello, This is in regard to the use of `ibv_modify_srq'
Sayantan call. When I use this call, I get a segmentation
Sayantan fault.
This is because the modify SRQ operation is not implemented at all in
libmthca. Do you just want to set the SRQ limit? That's not so hard
for me
Roland,
* On Oct,2 Roland Dreier[EMAIL PROTECTED] wrote :
Sayantan Hello, This is in regard to the use of `ibv_modify_srq'
Sayantan call. When I use this call, I get a segmentation
Sayantan fault.
This is because the modify SRQ operation is not implemented at all in
libmthca.
Sayantan If you could implement this feature, that would be
Sayantan really great!
OK, there's not much left to do. I should have something to check in
today. I'll let you know when it's ready.
- R.
___
openib-general mailing list
OK, I just checked in an initial implementation of both setting the
SRQ limit with the modify SRQ verb, and also getting SRP limit reached
events when the occur. You will need to update your kernel drivers,
libibverbs and libmthca to get this.
I've done zero testing, so please let me know how it
Roland,
* On Oct,5 Roland Dreier[EMAIL PROTECTED] wrote :
OK, I just checked in an initial implementation of both setting the
SRQ limit with the modify SRQ verb, and also getting SRP limit reached
events when the occur. You will need to update your kernel drivers,
libibverbs and libmthca to
On Wed, 2005-10-05 at 15:09 -0400, Sayantan Sur wrote:
This is because the modify SRQ operation is not implemented at all in
libmthca. Do you just want to set the SRQ limit? That's not so hard
for me to implement. However, you should be aware that as far as I
know, only mem-free HCAs
MattIs this due to memfree vs. memfull hardware or firmware
Matt difference? If you flash the memfull HCA with the memfree
Matt firmware (which I was told you can do) will the HCA generate
Matt an SRQ limit reached event?
I believe it's a firmware difference. There are
15 matches
Mail list logo
