On 29/01/2014 19:56, Bart Van Assche wrote:
On 01/29/14 16:06, Sagi Grimberg wrote:
Didn't understand why should it matter where the copy is done (iser/block)?
In the Linux kernel community it is considered important to avoid code
duplication. Hence the proposal to keep code that copies data
Hi,
Le jeudi 30 janvier 2014 à 01:33 +0200, Eli Cohen a écrit :
On Wed, Jan 29, 2014 at 09:48:43PM +0100, Yann Droneaud wrote:
Yann,
thanks for reviewing, your comments are helpful :-)
12 digits identifier are the norm for kernel. Please update your git
configuration:
git config
On 01/30/14 09:19, Or Gerlitz wrote:
On 29/01/2014 19:56, Bart Van Assche wrote:
On 01/29/14 16:06, Sagi Grimberg wrote:
Didn't understand why should it matter where the copy is done
(iser/block)?
In the Linux kernel community it is considered important to avoid code
duplication. Hence the
On 30/01/2014 12:07, Bart Van Assche wrote:
On 01/30/14 09:19, Or Gerlitz wrote:
Thanks for narrowing this down, I see your point, however the solution I
propose if to remove this copy altogether... for those rare cases where
fast-registration can't be done -- in SRP I think the code goes to
Commit c1be5232d21d Fix micro UAR allocator broke binary compatibility
between libmlx5 and mlx5_ib since it defines a different value to the number of
micro UARs per page, leading to wrong calculation in libmlx5. This patch
defines struct mlx5_ib_alloc_ucontext_req_v2 as an extension to struct
Hi,
Le jeudi 30 janvier 2014 à 13:49 +0200, Eli Cohen a écrit :
Commit c1be5232d21d Fix micro UAR allocator broke binary compatibility
between libmlx5 and mlx5_ib since it defines a different value to the number
of
micro UARs per page, leading to wrong calculation in libmlx5. This patch
Hello all,
I’m developing an (userspace) RDMA-application under Linux and came
across a problem, I’m not able to solve.
On machine A I had a chunk of memory registered with rdma_reg_read(),
so others can read from that memory later.
Machine B has memory which is also registered with
There is a new 3.3.17 release of OpenSM.
Tarball is available in:
http://www.openfabrics.org/downloads/management/
(listed in http://www.openfabrics.org/downloads/management/latest.txt)
md5sum:
9c1b85e47ab495110c1944e0f4d634b7 opensm-3.3.17.tar.gz
All component versions are from recent master
On Wed, Jan 29, 2014, Dan Carpenter dan.carpen...@oracle.com wrote:
We use tx_desc again after we free it.
yep, this is legacy code which isn't much of use over the last years
and hence the bug went in unnoticed
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
diff --git
On Thu, Jan 30, 2014 at 11:04 PM, Or Gerlitz or.gerl...@gmail.com wrote:
On Wed, Jan 29, 2014, Dan Carpenter dan.carpen...@oracle.com wrote:
We use tx_desc again after we free it.
yep, this is legacy code which isn't much of use over the last years
and hence the bug went in unnoticed
Hannes,
Have you tried marking the memory that is being read as volatile?
--Anuj
On Thu, Jan 30, 2014 at 1:45 PM, Hannes Weisbach
hannes.weisb...@tu-dresden.de wrote:
Hello all,
I'm developing an (userspace) RDMA-application under Linux and came
across a problem, I'm not able to solve.
On
There is a new 0.6 release of ibsim.
Tarball is available in:
http://www.openfabrics.org/downloads/management/
(listed in http://www.openfabrics.org/downloads/management/latest.txt)
md5sum:
d08e196d980e7c88066b3e5e25bf5432 ibsim-0.6.tar.gz
All component versions are from recent master branch.
From: CQ Tang cq.t...@intel.com
Improve performance by changing the behavour of the driver when all SDMA
descriptors are in use, and the processes adding new descriptors are
single- or multi-rail.
For single-rail processes, the driver will block the call and finish
posting all SDMA descriptors
13 matches
Mail list logo
