From: Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: Linux RDMA list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org,
Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Subject: Re: Re: Possible process deadlock in RMPP flow
Date: Sun, 04 Oct 2009 09:04:09 +0200 [thread overview]
Message-ID: <4AC848E9.6040909@voltaire.com> (raw)
In-Reply-To: <20090924073601.GA28876@mtls03>
Eli Cohen wrote:
> Thanks Or. This one is already in OFED 1.4.2 but apparently this is a
> different problem. Once I have information whether the patch Roland
> posted fixed it I will update the list.
Eli, did you find a commit that fixes the problem you reported on?
Or.
next prev parent reply other threads:[~2009-10-04 7:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 15:04 Possible process deadlock in RMPP flow Eli Cohen
2009-09-23 16:08 ` Sean Hefty
[not found] ` <7A32EEE20DF5432CADB60B8F8B1E0093-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-09-23 16:20 ` Hal Rosenstock
2009-09-23 17:25 ` Eli Cohen
2009-09-24 6:38 ` Or Gerlitz
[not found] ` <4ABB13F3.1060702-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2009-09-24 7:36 ` Eli Cohen
2009-09-24 15:53 ` Sean Hefty
[not found] ` <53F5ED0C557B4667B22A27A0459B800B-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-09-27 8:01 ` Eli Cohen
2009-10-04 7:04 ` Or Gerlitz [this message]
[not found] ` <4AC8BE74.3050200@mellanox.co.il>
[not found] ` <4AC8BE74.3050200-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
2009-10-19 20:30 ` Sean Hefty
[not found] ` <BFC792E8570C48B8981C34F913243887-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-10-20 6:06 ` [ewg] " Tziporet Koren
2009-10-20 7:48 ` Eli Cohen
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=4AC848E9.6040909@voltaire.com \
--to=ogerlitz-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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