mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-09-06 02:50:43 +00:00
![]() This PR contains a replacement driver for Intel iWarp hardware. This new driver supports the old ethernet hardware and also newer chips that can do ROCE. Otherwise this contains the typical mix of patches: - Driver updates and cleanups for bnxt_re, cxgb4, mlx4, and mlx5 - Many static checker driven code clean ups, including a wide refcount_t conversion - Several series for the hns driver, more HIP09 HW capabilities, migration to new HW register manipulators, and code cleanups - Minor fixes and improvements in srp, rts, and cm - Improvements throughout for sysfs related code to use DEVICE_ATTR_*, make the ib_port sysfs first-class, and overall use sysfs APIs properly - Intel's new irdma driver replacing i40iw - rxe general clean ups and Memory Window support -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfB7FMLh+8QxL+6i3OG33FX4gmxoFAmDcunQACgkQOG33FX4g mxqSBA//dsZi/UzpzgU+YqyMFmUp04wd2/iCYzOcCViNPQZCyCARbGaMXI4kMa4s 8dM5xU76OnCuNSnXHaIwvHC3CdN9GUm08j9eWY7syvAiKtXCjzv7qmCVfBw35UyK IXKfXh57toTSSAIfxw8yKc97QgaDSJ2zQ34fXkoE0AvTlfyN6pHQe9ef/Ca0ejS4 awUGYVG/oilLXrEHcSSAv5UoX6hOUje6jqqRgp5jmZTI3g7SlIPL8mWgXBkHAYmd kDX7lBd09CKo2bmR071/kF6xUzvbCg1tmeE6lZze7gE+aKlBkZcvCBe1RAh3sBzK ysLfON5GGw5qnkMaY8j5h3sgWvi3qTTEW+jCAmmVi/6z4PF47mvmVVn+/pZc3y2e PqH43cunhwS0KuoUJ5Sd48J/UvabrvdbCNZrjCGCpt45EF4VwKxYMh74Bf0ABEQS i9eKR/+wyHG6Uv1U37fIXsqa8yUttl9aV/s88s8irn4xhG8ygBLZgeVQNeGUfvdV 1W0XLEjRmKFezC1FhiPOz7CLIgL3BfSU1V+S7p0Gvb6ijZqyZTfRUaWbaD3KJpRT 1kwzE4qp6IbJMEqgQH/lq0xBzvzF48FPvBslX5kwlm0phQRrMCwMVIafutpu395q ySeStEvsTVfz/JUHL3ZaEJyTRjAvPL0lXLH80XUpgWk9GzsksOM= =wyqt -----END PGP SIGNATURE----- Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma Pull rdma updates from Jason Gunthorpe: "This contains a replacement driver for Intel iWarp hardware. This new driver supports the old ethernet hardware and also newer chips that can do ROCE. Other than that, this contains the typical mix of patches: - Driver updates and cleanups for bnxt_re, cxgb4, mlx4, and mlx5 - Many static checker driven code clean ups, including a wide refcount_t conversion - Several series for the hns driver, more HIP09 HW capabilities, migration to new HW register manipulators, and code cleanups - Minor fixes and improvements in srp, rts, and cm - Improvements throughout for sysfs related code to use DEVICE_ATTR_*, make the ib_port sysfs first-class, and overall use sysfs APIs properly - Intel's new irdma driver replacing i40iw - rxe general clean ups and Memory Window support" * tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma: (211 commits) RDMA/core: Always release restrack object RDMA/mlx5: Don't access NULL-cleared mpi pointer RDMA/irdma: Fix potential overflow expression in irdma_prm_get_pbles RDMA/irdma: Check contents of user-space irdma_mem_reg_req object RDMA/rxe: Missing unlock on error in get_srq_wqe() RDMA/cma: Fix rdma_resolve_route() memory leak RDMA/core/sa_query: Remove unused argument RDMA/cma: Fix incorrect Packet Lifetime calculation RDMA/cma: Protect RMW with qp_mutex RDMA/cma: Remove unnecessary INIT->INIT transition RDMA/hns: Add window selection field of congestion control RDMA/hfi1: Remove use of kmap() RDMA/irdma: Remove use of kmap() RDMA/bnxt_re: Fix uninitialized struct bit field rsvd1 IB/isert: Align target max I/O size to initiator size RDMA/hns: Fix incorrect vlan enable bit in QPC MAINTAINERS: Update Broadcom RDMA maintainers RDMA/irdma: Use the queried port attributes RDMA/rxe: Fix redundant skb_put_zero RDMA/rxe: Fix extra copy in prepare_ack_packet ... |
||
---|---|---|
.. | ||
Kconfig | ||
Makefile | ||
README | ||
rnbd-clt-sysfs.c | ||
rnbd-clt.c | ||
rnbd-clt.h | ||
rnbd-common.c | ||
rnbd-log.h | ||
rnbd-proto.h | ||
rnbd-srv-dev.c | ||
rnbd-srv-dev.h | ||
rnbd-srv-sysfs.c | ||
rnbd-srv.c | ||
rnbd-srv.h |
******************************** RDMA Network Block Device (RNBD) ******************************** Introduction ------------ RNBD (RDMA Network Block Device) is a pair of kernel modules (client and server) that allow for remote access of a block device on the server over RTRS protocol using the RDMA (InfiniBand, RoCE, iWARP) transport. After being mapped, the remote block devices can be accessed on the client side as local block devices. I/O is transferred between client and server by the RTRS transport modules. The administration of RNBD and RTRS modules is done via sysfs entries. Requirements ------------ RTRS kernel modules Quick Start ----------- Server side: # modprobe rnbd_server Client side: # modprobe rnbd_client # echo "sessname=blya path=ip:10.50.100.66 device_path=/dev/ram0" > \ /sys/devices/virtual/rnbd-client/ctl/map_device Where "sessname=" is a session name, a string to identify the session on client and on server sides; "path=" is a destination IP address or a pair of a source and a destination IPs, separated by comma. Multiple "path=" options can be specified in order to use multipath (see RTRS description for details); "device_path=" is the block device to be mapped from the server side. After the session to the server machine is established, the mapped device will appear on the client side under /dev/rnbd<N>. RNBD-Server Module Parameters ============================= dev_search_path --------------- When a device is mapped from the client, the server generates the path to the block device on the server side by concatenating dev_search_path and the "device_path" that was specified in the map_device operation. The default dev_search_path is: "/". dev_search_path option can also contain %SESSNAME% in order to provide different device namespaces for different sessions. See "device_path" option for details. ============================ Protocol (rnbd/rnbd-proto.h) ============================ 1. Before mapping first device from a given server, client sends an RNBD_MSG_SESS_INFO to the server. Server responds with RNBD_MSG_SESS_INFO_RSP. Currently the messages only contain the protocol version for backward compatibility. 2. Client requests to open a device by sending RNBD_MSG_OPEN message. This contains the path to the device and access mode (read-only or writable). Server responds to the message with RNBD_MSG_OPEN_RSP. This contains a 32 bit device id to be used for IOs and device "geometry" related information: side, max_hw_sectors, etc. 3. Client attaches RNBD_MSG_IO to each IO message send to a device. This message contains device id, provided by server in his rnbd_msg_open_rsp, sector to be accessed, read-write flags and bi_size. 4. Client closes a device by sending RNBD_MSG_CLOSE which contains only the device id provided by the server. ========================================= Contributors List(in alphabetical order) ========================================= Danil Kipnis <danil.kipnis@profitbricks.com> Fabian Holler <mail@fholler.de> Guoqing Jiang <guoqing.jiang@cloud.ionos.com> Jack Wang <jinpu.wang@profitbricks.com> Kleber Souza <kleber.souza@profitbricks.com> Lutz Pogrell <lutz.pogrell@cloud.ionos.com> Milind Dumbare <Milind.dumbare@gmail.com> Roman Penyaev <roman.penyaev@profitbricks.com> Swapnil Ingle <ingleswapnil@gmail.com>