Its been 2 months since I posted this.
What is the current status? Last comment I saw was from Ira
saying either add this functionality to ibportstate or
rename ibportstate but don't split it off into a new command.
My preference is to go with the original patch. I haven't
seen any strong objection
>Currently, the RDS code sets both of these to 1 when calling
>rdma_accept(). Using an arbitrary greater value (e.g. 64) doesn't seem
>to work right.
>
>I can call ib_query_qp(). Am I to assume I can set initiator_depth up to
>ib_qp_attr.max_rd_atomic, and responder_resources to
>ib_qp_attr.max_des
Hi all,
Currently, the RDS code sets both of these to 1 when calling
rdma_accept(). Using an arbitrary greater value (e.g. 64) doesn't seem
to work right.
I can call ib_query_qp(). Am I to assume I can set initiator_depth up to
ib_qp_attr.max_rd_atomic, and responder_resources to
ib_qp_attr.max_d
New release for uDAPL 2.0 available on the OFA download page and in my git tree.
Bug fixes for RDMAoE.
md5sum: 32924de6b4f1fa351aa1468b19501981 dapl-2.0.26.tar.gz
Summary of changes since last release:
Release 2.0.26 fixes (tested on OFED-RDMAoE-rc6, Mellanox MHJH29-XTC, v2.7.0):
v2 - op
Chris Worley, on 01/09/2010 01:39 AM wrote:
I thought if the device was opened with the O_DIRECT flag, then the
scheduler should have nothing to coalesce.
Depends on how many I/Os your application has in flight at once,
assuming it is using AIO or threads. If you have more requests in flight
tha
> I wonder if the overflow check could be removed all together and be
> left to the ULP (kernel is trusted environment...) is there any risk
> in doing so? this way the WR posting code will not experience
> contention with the poll WC code on the CQ lock.
We could do that I guess if it's a re
Or Gerlitz wrote:
Hi Vlad, I came across this ofed patch which isn't upstream. Is it a must
for making mlx4/ib/4K mtu working? was it rejected from upstream? why?
Or.
Hi Or,
Yes, it is must for mlx4/ib/4K mtu.
I forgot to send it upstream.
I'll do this shortly.
Thanks,
Vladimir
mlx4/IB: A
On Tue, Jan 5, 2010 at 5:32 AM, Eli Cohen wrote:
> Add support for RoCEE device binding and IP --> GID resolution. Path resolving
> and multicast joining are implemented within cma.c by filling the responses
> and
> pushing the callbacks to the cma work queue. IP->GID resolution always yields
> I
Hi Sasha,
On Mon, Dec 28, 2009 at 4:22 AM, Sasha Khapyorsky wrote:
> Hi Ira,
>
> On 09:35 Mon 21 Dec , Sasha Khapyorsky wrote:
>>
>> An errors are response timeouts. I guess that most of them are due
>> to switches' VL15 overflow (could be verified by VL15Dropped counter
>> evaluation). Will
Jack, I see now that commit cd155c1 "IB/mlx4: Fix creation of kernel QP with
max number of send s/g entries" is mainstream but not ofed 1.4.x and that
mlx4_0090_fix_sq_wrs.patch (below) is in ofed but not mainstream, was it
rejected from the mainline kernel? why?
Or.
1. Limit qp resources acc
Hi Vlad, I came across this ofed patch which isn't upstream. Is it a must
for making mlx4/ib/4K mtu working? was it rejected from upstream? why?
Or.
mlx4/IB: Add set_4k_mtu module parameter.
It control Infiniband link MTU for all IB ports in a host.
Signed-off-by: Vladimir Sokolovsky
---
Inde
On Thu, Jan 07, 2010 at 11:24:51AM -0700, Jason Gunthorpe wrote:
> On Thu, Jan 07, 2010 at 08:50:47AM -0800, Sean Hefty wrote:
> > >> > + route->path_rec->hop_limit = 2;
> > >>
> > >
> > >The reason is that ib_init_ah_from_path() will not set IB_AH_GRH for
> > >hop_limit smaller then 2, and si
As of commit f56bcd8 "IPoIB: Use separate CQ for UD send completions",
there are no TX interrupts at the main code path. Change the ethtool
related code to comply with this, such the users will not be misleaded
to assume they can control TX interrupt moderation. Was pointed by
Alex Vainman
Signed
Hi,
I modified the perftest program ib_read_bw to use sge lists. The length of each
sge is 1 (one) byte. I configured the QP to support up to 32 sges (aligned with
the capabilities of the device).
Now, everything works correct up to 30 sges. Using 31 or 32 sges, I receive 29
bytes in both cas
Currently, if dumping SA DB is enabled, the file is dumped
at every sweep. This patch adds "dirty" flag that denotes
whether the SA DB needs to be dumped or not.
SA DB contains 3 types of data:
- informinfo records
- service records
- mcmember records
So the flag must be set in 6 places:
- ad
Hi Sasha,
On 26/Nov/09 16:15, Sasha Khapyorsky wrote:
On 13:01 Wed 04 Nov , Yevgeny Kliteynik wrote:
Optimizing SA DB dump - added "dirty" flag to denote
that the SA DB was modified, so that the DB will be
dumped only when the flag is on.
[v2 - no changes, just rebased and resolved conflic
16 matches
Mail list logo