If user requested signature enable we Initialize
relevant mlx5_ib_qp members. we mark the qp as sig_enable
and we check if wqe_size will fit compound REG_SIG_MR work
request (UMR + 2 x SET_PSV wqes), if computed wqe_size is
smaller we align wqe_size to MLX5_SIG_WQE_SIZE.
Signed-off-by: Sagi
Support create_mr and destroy_mr verbs.
For now, create/destroy routines will only support user request
for signature enabled memory regions. The created memory region
will be an indirect memory key that will be able to register
pre-registered data buffer and protection guards buffer
This commit takes care of the generated signature
error cqe generated by the HW (if happened). The
underlying mlx5 driver will handle signature error
completions and will lookup the relevant memory region
(under a read_lock) and mark it as dirty (contains a
signature error).
Once the user will
This commit introduces verbs for creating/destoying memory
regions which will allow new types of memory key operations such
as protected memory registration.
Indirect memory registration is registering several (one
of more) pre-registered memory regions in a specific layout.
The Indirect region
This commit Introduces the Verbs Interface for signature related
operations. A signature handover operation shall configure the
layouts of data and protection attributes both in memory and wire
domains.
Signature operations are:
- INSERT
Generate and insert protection information when handing
This radix tree will be useful when processing signature
errors on a specific key. The mlx5 driver shall lookup the
matching mlx5 memory region structure and mark it as
dirty (contains signature errors). The radix tree is protected
under a rw_lock as signature error processing is guaranteed not
to
This patchset Introduces Verbs level support for signature handover feature.
Siganture is intended to implement end-to-end data integrity on a transactional
basis in a completely offloaded manner.
There are several end-to-end data integrity methods used today in various
applications and/or upper
Currently support only T10-DIF types of signature
handover operations (typs 1|2|3).
Signed-off-by: Sagi Grimberg sa...@mellanox.com
---
drivers/infiniband/hw/mlx5/main.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/drivers/infiniband/hw/mlx5/main.c
This patch implements IB_WR_REG_SIG_MR posted by the user.
Baisically this WR involvs 3 WQEs in order to prepare and properly
register the signature layout:
1. post UMR WR to register the sig_mr in one of two possible ways:
* In case the user registered a single MR for data so the UMR data
get_umr_flags helper function might be used for types
of access modes other than ACCESS_MODE_MTT, such as
ACCESS_MODE_KLM. so remove it from helper and caller
will add it's own access mode flag.
This commit does not add/change functionality.
Signed-off-by: Sagi Grimberg sa...@mellanox.com
---
From: Kumar Sanghvi kuma...@chelsio.com
IPv6 uses 2 TIDs with CLIP enabled and 4 TIDs without CLIP.
Currently we are incrementing STIDs in use by 1 for both IPv4 and IPv6 which
is wrong.
Further, driver currently does not have interface to query if CLIP is programmed
for particular IPv6 address.
From: Kumar Sanghvi kuma...@chelsio.com
Signed-off-by: Hariprasad Shenai haripra...@chelsio.com
Signed-off-by: Kumar Sanghvi kuma...@chelsio.com
---
drivers/infiniband/hw/cxgb4/cm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/infiniband/hw/cxgb4/cm.c
From: Kumar Sanghvi kuma...@chelsio.com
Based on original work by Santosh Rastapur sant...@chelsio.com
Signed-off-by: Hariprasad Shenai haripra...@chelsio.com
Signed-off-by: Kumar Sanghvi kuma...@chelsio.com
---
drivers/infiniband/hw/cxgb4/cm.c | 4 +---
1 file changed, 1 insertion(+), 3
From: Kumar Sanghvi kuma...@chelsio.com
The LE workaround code is incorrectly reusing the TCAM TIDs
(meant for allocation by firmware in case of hash collisions) for filter
servers. This patch assigns the filter server TIDs properly starting from
sftid_base index.
Based on original work by
From: Kumar Sanghvi kuma...@chelsio.com
When creating offload server entries, an IPv6 passive connection request
can trigger a reply with a null STID, whereas the driver would expect
the reply 'STID to match the value used for the request.
This happens due to h/w limitation on T4 and T5.
This
From: Kumar Sanghvi kuma...@chelsio.com
Adds API cxgb4_select_ntuple so as to enable Upper Level Drivers to correctly
calculate the tuple fields.
Adds constant definitions for TP_VLAN_PRI_MAP for the Compressed
Filter Tuple field widths and structures and uses them.
Also, the CPL Parameters
From: Kumar Sanghvi kuma...@chelsio.com
Signed-off-by: Hariprasad Shenai haripra...@chelsio.com
Signed-off-by: Kumar Sanghvi kuma...@chelsio.com
---
drivers/infiniband/hw/cxgb4/cm.c | 71 ++--
1 file changed, 17 insertions(+), 54 deletions(-)
diff --git
From: Kumar Sanghvi kuma...@chelsio.com
We were creating LE Workaround Server Filters without specifying
IPPROTO_TCP (6) in the filters (when F_PROTOCOL is set in TP_VLAN_PRI_MAP).
This meant that UDP packets with matching IP Addresses/Ports would get
caught up in the filter and be delivered to
From: Kumar Sanghvi kuma...@chelsio.com
When creating server filters via LE-Workaround path, properly track
the server filter entries, and don't confuse them with regular
server entries.
Based on original work by Hariprasad Shenai haripra...@chelsio.com
Signed-off-by: Hariprasad Shenai
Hi All,
This patch series provides miscelleneous fixes for Chelsio T4/T5 adapters
related to server entries and server filter entries.
Also, fixes a bug in ULD (Upper Level Driver) like iw_cxgb4 where-in it
calculates wrong tuple values
on T5 adapter. So, a new API cxgb4_select_ntuple is
Signed-off-by: Ilya Nelkenbaum il...@mellanox.com
---
Changes since version 1:
- all method declarations were removed from 'ssa_smdb.h'
- argument types were changed back from 'void*' to
specific types
include/infiniband/ssa_smdb.h | 26 --
Please ignore.
On 12/16/2013 3:30 PM, Ilya Nelkenbaum wrote:
Signed-off-by: Ilya Nelkenbaum il...@mellanox.com
---
Changes since version 1:
- all method declarations were removed from 'ssa_smdb.h'
- argument types were changed back from 'void*' to
specific types
OK, I finally got to merge this to libibverbs. Please take a look at
my libibverbs git tree and let me know if there is any issue with the
verbs extensions or XRC support.
I will probably cut a new libibverbs release in about a week if this
looks good to everyone.
Thanks!
Roland
--
To
On Mon, Dec 16, 2013 at 9:16 PM, Roland Dreier rol...@purestorage.com wrote:
OK, I finally got to merge this to libibverbs. Please take a look at
my libibverbs git tree and let me know if there is any issue with the
verbs extensions or XRC support.
Roland, your libibverbs tree which includes
On Thu, Dec 12, 2013, Or Gerlitz ogerl...@mellanox.com wrote:
Changes from V5:
- moved the address resolution helper from the uverbs layer to the
ib_core module where it belongs. This will also allow to run kernel
consumers who don't use the rdma-cm
Hi Roland,
Anything else, or we
25 matches
Mail list logo
