[LU-9680] Improve the user land to kernel space interface for lustre

• Type: Improvement
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Lustre 2.11.0
• Fix Version/s: Upstream
• Assignee: James A Simmons
• Reporter: James A Simmons

Description

Lustre currently has a complex assortment of ioctls for both the file system component and the LNet layer. Many of the those ioctls are no longer used or can be replaced with accessing files in the sysfs or debugfs file systems. With the initial review of lustre in the upstream kernel two topics on how ioctls are managed to brought to our attention. One is the dislike of the ioctl redirection that is done in lustre. The seconds is the request that we use the netlink userland API, in particular with the LNet layer. The netlink API could also be used for lustre.

Issue Links

• is related to: LU-8915 Don't use linux list structure as user land arguments for lnet selftest
• is related to: LU-11850 Relocating /proc/fs/lustre/ost to /sys/kenrnel/debug/lustre/ost prevents non-root access
• is related to: LU-14391 Large network routes
• is related to: LU-12198 lnetctl peer show hangs for ~2600 clients, ioctl getting E2BIG
• is related to: LU-14732 struct hsm_user_request extent fields set to random values.
• is related to: LU-12511 Prepare lustre for adoption into the linux kernel
• is related to: LU-14680 remove strict dependency between user tools and kernel RPMs
• is related to: LU-6202 clean up ioctl handling
• is related to: LU-8834 Don't hide new functionality behind ioctls.
• is related to: LU-9667 LNet Kernel/Userspace Interface
• is related to: LU-7659 Replace KUC by more standard mechanisms
• is related to: LU-10968 add coordinator bypass upcalls for HSM archive and remove