Linux-RDMA Archive on lore.kernel.org
 help / color / Atom feed
[PATCH] IB/hfi1: remove redundant assignment to variable ret
 2019-11-22 17:54 UTC  (2+ messages) - mbox.gz / Atom

[PATCH rdma-next v1 00/48] Organize code according to IBTA layout
 2019-11-22 16:52 UTC  (54+ messages) - mbox.gz / Atom
` [PATCH rdma-next v1 01/48] RDMA/cm: Provide private data size to CM users
` [PATCH rdma-next v1 02/48] RDMA/srpt: Use private_data_len instead of hardcoded value
` [PATCH rdma-next v1 03/48] RDMA/ucma: Mask QPN to be 24 bits according to IBTA
` [PATCH rdma-next v1 04/48] RDMA/cm: Add SET/GET implementations to hide IBA wire format
` [PATCH rdma-next v1 05/48] RDMA/cm: Request For Communication (REQ) message definitions
` [PATCH rdma-next v1 06/48] RDMA/cm: Message Receipt Acknowledgment (MRA) "
` [PATCH rdma-next v1 07/48] RDMA/cm: Reject (REJ) "
` [PATCH rdma-next v1 08/48] RDMA/cm: Reply To Request for communication (REP) definitions
` [PATCH rdma-next v1 09/48] RDMA/cm: Ready To Use (RTU) definitions
` [PATCH rdma-next v1 10/48] RDMA/cm: Request For Communication Release (DREQ) definitions
` [PATCH rdma-next v1 11/48] RDMA/cm: Reply To Request For Communication Release (DREP) definitions
` [PATCH rdma-next v1 12/48] RDMA/cm: Load Alternate Path (LAP) definitions
` [PATCH rdma-next v1 13/48] RDMA/cm: Alternate Path Response (APR) message definitions
` [PATCH rdma-next v1 14/48] RDMA/cm: Service ID Resolution Request (SIDR_REQ) definitions
` [PATCH rdma-next v1 15/48] RDMA/cm: Service ID Resolution Response (SIDR_REP) definitions
` [PATCH rdma-next v1 16/48] RDMA/cm: Convert QPN and EECN to be u32 variables
` [PATCH rdma-next v1 17/48] RDMA/cm: Convert REQ responded resources to the new scheme
` [PATCH rdma-next v1 18/48] RDMA/cm: Convert REQ initiator depth "
` [PATCH rdma-next v1 19/48] RDMA/cm: Convert REQ remote response timeout
` [PATCH rdma-next v1 20/48] RDMA/cm: Simplify QP type to wire protocol translation
` [PATCH rdma-next v1 21/48] RDMA/cm: Convert REQ flow control
` [PATCH rdma-next v1 22/48] RDMA/cm: Convert starting PSN to be u32 variable
` [PATCH rdma-next v1 23/48] RDMA/cm: Update REQ local response timeout
` [PATCH rdma-next v1 24/48] RDMA/cm: Convert REQ retry count to use new scheme
` [PATCH rdma-next v1 25/48] RDMA/cm: Update REQ path MTU field
` [PATCH rdma-next v1 26/48] RDMA/cm: Convert REQ RNR retry timeout counter
` [PATCH rdma-next v1 27/48] RDMA/cm: Convert REQ MAX CM retries
` [PATCH rdma-next v1 28/48] RDMA/cm: Convert REQ SRQ field
` [PATCH rdma-next v1 29/48] RDMA/cm: Convert REQ flow label field
` [PATCH rdma-next v1 30/48] RDMA/cm: Convert REQ packet rate
` [PATCH rdma-next v1 31/48] RDMA/cm: Convert REQ SL fields
` [PATCH rdma-next v1 32/48] RDMA/cm: Convert REQ subnet local fields
` [PATCH rdma-next v1 33/48] RDMA/cm: Convert REQ local ack timeout
` [PATCH rdma-next v1 34/48] RDMA/cm: Convert MRA MRAed field
` [PATCH rdma-next v1 35/48] RDMA/cm: Convert MRA service timeout
` [PATCH rdma-next v1 36/48] RDMA/cm: Update REJ struct to use new scheme
` [PATCH rdma-next v1 37/48] RDMA/cm: Convert REP target ack delay field
` [PATCH rdma-next v1 38/48] RDMA/cm: Convert REP failover accepted field
` [PATCH rdma-next v1 39/48] RDMA/cm: Convert REP flow control field
` [PATCH rdma-next v1 40/48] RDMA/cm: Convert REP RNR retry count field
` [PATCH rdma-next v1 41/48] RDMA/cm: Convert REP SRQ field
` [PATCH rdma-next v1 42/48] RDMA/cm: Delete unused CM LAP functions
` [PATCH rdma-next v1 43/48] RDMA/cm: Convert LAP flow label field
` [PATCH rdma-next v1 44/48] RDMA/cm: Convert LAP fields
` [PATCH rdma-next v1 45/48] RDMA/cm: Delete unused CM ARP functions
` [PATCH rdma-next v1 46/48] RDMA/cm: Convert SIDR_REP to new scheme
` [PATCH rdma-next v1 47/48] RDMA/cm: Add Enhanced Connection Establishment (ECE) bits
` [PATCH rdma-next v1 48/48] RDMA/cm: Convert private_date access

[PATCH rdma-next 0/4] Get IB port and node GUIDs through rtnetlink
 2019-11-22 16:21 UTC  (7+ messages) - mbox.gz / Atom
` [PATCH rdma-next 1/4] net/core: Add support for getting VF GUIDs

[net-next v2 1/1] virtual-bus: Implementation of Virtual Bus
 2019-11-22 16:19 UTC  (52+ messages) - mbox.gz / Atom

[PATCH v7 00/24] mm/gup: track dma-pinned pages: FOLL_PIN
 2019-11-22 11:15 UTC  (50+ messages) - mbox.gz / Atom
` [PATCH v7 01/24] mm/gup: pass flags arg to __gup_device_* functions
` [PATCH v7 02/24] mm/gup: factor out duplicate code from four routines
` [PATCH v7 03/24] mm/gup: move try_get_compound_head() to top, fix minor issues
` [PATCH v7 04/24] mm: Cleanup __put_devmap_managed_page() vs ->page_free()
` [PATCH v7 05/24] mm: devmap: refactor 1-based refcounting for ZONE_DEVICE pages
` [PATCH v7 06/24] goldish_pipe: rename local pin_user_pages() routine
` [PATCH v7 07/24] IB/umem: use get_user_pages_fast() to pin DMA pages
` [PATCH v7 08/24] media/v4l2-core: set pages dirty upon releasing DMA buffers
` [PATCH v7 09/24] vfio, mm: fix get_user_pages_remote() and FOLL_LONGTERM
` [PATCH v7 10/24] mm/gup: introduce pin_user_pages*() and FOLL_PIN
` [PATCH v7 11/24] goldish_pipe: convert to pin_user_pages() and put_user_page()
` [PATCH v7 12/24] IB/{core,hw,umem}: set FOLL_PIN via pin_user_pages*(), fix up ODP
` [PATCH v7 13/24] mm/process_vm_access: set FOLL_PIN via pin_user_pages_remote()
` [PATCH v7 14/24] drm/via: set FOLL_PIN via pin_user_pages_fast()
` [PATCH v7 15/24] fs/io_uring: set FOLL_PIN via pin_user_pages()
` [PATCH v7 16/24] net/xdp: "
` [PATCH v7 17/24] mm/gup: track FOLL_PIN pages
` [PATCH v7 18/24] media/v4l2-core: pin_user_pages (FOLL_PIN) and put_user_page() conversion
` [PATCH v7 19/24] vfio, mm: "
` [PATCH v7 20/24] powerpc: book3s64: convert to pin_user_pages() and put_user_page()
` [PATCH v7 21/24] mm/gup_benchmark: use proper FOLL_WRITE flags instead of hard-coding "1"
` [PATCH v7 22/24] mm/gup_benchmark: support pin_user_pages() and related calls
` [PATCH v7 23/24] selftests/vm: run_vmtests: invoke gup_benchmark with basic FOLL_PIN coverage
` [PATCH v7 24/24] mm, tree-wide: rename put_user_page*() to unpin_user_page*()

[PATCH net] net: rtnetlink: prevent underflows in do_setvfinfo()
 2019-11-22  7:21 UTC  (5+ messages) - mbox.gz / Atom

[question]can hard roce and soft roce communicate with each other?
 2019-11-22  7:19 UTC  - mbox.gz / Atom

[PATCH rdma-core 0/7] libhns: Bugfix for hip08
 2019-11-22  6:40 UTC  (12+ messages) - mbox.gz / Atom
` [PATCH rdma-core 1/7] libhns: Fix calculation errors with ilog32()
` [PATCH rdma-core 2/7] libhns: Optimize bind_mw for fixing null pointer access
` [PATCH rdma-core 3/7] libhns: Bugfix for assigning sl
` [PATCH rdma-core 4/7] libhns: Bugfix for cleaning cq
` [PATCH rdma-core 5/7] libhns: Bugfix for updating qp params
` [PATCH rdma-core 6/7] libhns: Avoid null pointer operation
` [PATCH rdma-core 7/7] libhns: Return correct value of cqe num when flushing cqe failed

[PATCH AUTOSEL 4.4 29/68] IB/qib: Fix an error code in qib_sdma_verbs_send()
 2019-11-22  6:12 UTC  (2+ messages) - mbox.gz / Atom
` [PATCH AUTOSEL 4.4 35/68] RDMA/srp: Propagate ib_post_send() failures to the SCSI mid-layer

[PATCH AUTOSEL 4.9 27/91] net/mlx5: Continue driver initialization despite debugfs failure
 2019-11-22  6:00 UTC  (3+ messages) - mbox.gz / Atom
` [PATCH AUTOSEL 4.9 36/91] IB/qib: Fix an error code in qib_sdma_verbs_send()
` [PATCH AUTOSEL 4.9 42/91] RDMA/srp: Propagate ib_post_send() failures to the SCSI mid-layer

[PATCH AUTOSEL 4.14 011/127] RDMA/vmw_pvrdma: Use atomic memory allocation in create AH
 2019-11-22  5:54 UTC  (5+ messages) - mbox.gz / Atom
` [PATCH AUTOSEL 4.14 038/127] net/mlx5: Continue driver initialization despite debugfs failure
` [PATCH AUTOSEL 4.14 050/127] IB/qib: Fix an error code in qib_sdma_verbs_send()
` [PATCH AUTOSEL 4.14 059/127] RDMA/srp: Propagate ib_post_send() failures to the SCSI mid-layer
` [PATCH AUTOSEL 4.14 074/127] IB/rxe: Make counters thread safe

[PATCH AUTOSEL 4.19 030/219] RDMA/hns: Fix the bug while use multi-hop of pbl
 2019-11-22  5:49 UTC  (12+ messages) - mbox.gz / Atom
` [PATCH AUTOSEL 4.19 032/219] RDMA/vmw_pvrdma: Use atomic memory allocation in create AH
` [PATCH AUTOSEL 4.19 087/219] net/mlx5: Continue driver initialization despite debugfs failure
` [PATCH AUTOSEL 4.19 103/219] IB/qib: Fix an error code in qib_sdma_verbs_send()
` [PATCH AUTOSEL 4.19 112/219] RDMA/srp: Propagate ib_post_send() failures to the SCSI mid-layer
` [PATCH AUTOSEL 4.19 129/219] IB/rxe: Make counters thread safe
` [PATCH AUTOSEL 4.19 160/219] infiniband: bnxt_re: qplib: Check the return value of send_message
` [PATCH AUTOSEL 4.19 161/219] infiniband/qedr: Potential null ptr dereference of qp
` [PATCH AUTOSEL 4.19 211/219] RDMA/hns: Fix the bug with updating rq head pointer when flush cqe
` [PATCH AUTOSEL 4.19 212/219] RDMA/hns: Bugfix for the scene without receiver queue
` [PATCH AUTOSEL 4.19 213/219] RDMA/hns: Fix the state of rereg mr
` [PATCH AUTOSEL 4.19 214/219] RDMA/hns: Use GFP_ATOMIC in hns_roce_v2_modify_qp

[PATCH rdma-core 0/4] pyverbs: Introduce parent domain
 2019-11-21 16:31 UTC  (6+ messages) - mbox.gz / Atom
` [PATCH rdma-core 2/4] pyverbs: Introduce ParentDomain class

[PATCH for-next v2 0/3] EFA RDMA read support
 2019-11-21 14:15 UTC  (4+ messages) - mbox.gz / Atom
` [PATCH for-next v2 1/3] RDMA/efa: Store network attributes in device attributes
` [PATCH for-next v2 2/3] RDMA/efa: Support remote read access in MR registration
` [PATCH for-next v2 3/3] RDMA/efa: Expose RDMA read related attributes

[PATCH RFC rdma-core] verbs: relaxed ordering memory regions
 2019-11-21 13:38 UTC  (3+ messages) - mbox.gz / Atom

[PATCH v2 0/6] Raspberry Pi 4 PCIe support
 2019-11-21 12:18 UTC  (4+ messages) - mbox.gz / Atom

[PATCH v2 rdma-next] RDMA/qedr: Add kernel capability flags for dpm enabled mode
 2019-11-21 11:29 UTC  - mbox.gz / Atom

[PATCH v3 for-next 0/2] Fix crash due to sleepy mutex while holding lock in post_{send|recv|poll}
 2019-11-21 11:20 UTC  (3+ messages) - mbox.gz / Atom
` [PATCH v3 for-next 1/2] RDMA/hns: Add the workqueue framework for flush cqe handler
` [PATCH v3 for-next 2/2] RDMA/hns: Delayed flush cqe process with workqueue

[PATCH rdma-next] RDMA/qedr: Add kernel capability flags for dpm enabled mode
 2019-11-21  8:12 UTC  (3+ messages) - mbox.gz / Atom
  ` [EXT] "

[PATCH V3 for-next 0/3] Broadcom's roce driver bug fixes
 2019-11-21  6:22 UTC  (4+ messages) - mbox.gz / Atom
` [PATCH V3 for-next 1/3] RDMA/bnxt_re: Fix chip number validation Broadcom's Gen P5 series
` [PATCH V3 for-next 2/3] RDMA/bnxt_re: fix stat push into dma buffer on gen p5 devices
` [PATCH V3 for-next 3/3] RDMA/bnxt_re: fix sparse warnings

[PATCH mlx5-next 0/5] Mellanox, mlx5-next updates 2019-11-20
 2019-11-20 22:22 UTC  (6+ messages) - mbox.gz / Atom
` [PATCH mlx5-next 1/5] net/mlx5: Add structures layout for new MCAM access reg groups
` [PATCH mlx5-next 2/5] net/mlx5: Read MCAM register groups 1 and 2
` [PATCH mlx5-next 3/5] net/mlx5: Add structures and defines for MIRC register
` [PATCH mlx5-next 4/5] net/mlx5: Don't write read-only fields in MODIFY_HCA_VPORT_CONTEXT command
` [PATCH mlx5-next 5/5] net/mlx5: Expose resource dump register mapping

[PATCH for-rc 0/3] Broadcom's roce dirver bug fixes
 2019-11-20 16:17 UTC  (5+ messages) - mbox.gz / Atom

page:   latest

Linux-RDMA Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-rdma/0 linux-rdma/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-rdma linux-rdma/ https://lore.kernel.org/linux-rdma \
		linux-rdma@vger.kernel.org
	public-inbox-index linux-rdma

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-rdma


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git