[lustre-devel] [PATCH v2 00/13] staging:lustre: split kernel comm between user and kernel

Greg Kroah-Hartman gregkh at linuxfoundation.org
Wed Feb 3 14:19:09 PST 2016


On Wed, Dec 23, 2015 at 04:24:39PM -0500, James Simmons wrote:
> The kernel communication code used for HSM and changelog is
> entangled. Move the user space bits into the liblustreapi. This will
> also help for a possible relicensing. The kernel portion is also moved
> from libcfs to obdclass.
> 
> The original libcfs_kernelcomm.h header is split into three parts:
> 
>   * lustre_kernelcomm.h, a new header for the kernel parts;
>   * uapi_kernelcomm.h, a new header for the data structures shared
>     between userspace and kernelspace;
>   * lustreapi_internal.h receives the private liblustreapi prototypes.
> 
> The original code in kernel_user_comm.c is split into two parts:
> 
>   * obdclass/kernelcomm.c for the kernel part. filp_user_write() was
>     moved there, and linux-fs.c deleted;
>   * liblustreapi_kernelconn.c for the user part. The calls to CDEBUG
>     have been removed, and calls to CERROR have been transformed to
>     llapi_err_noerrno. The type lustre_kernelcomm has been removed and
>     replace by struct lustre_kernelcomm.
> 
> Various names and filenames have been harmonized to *kernelcomm*.
> 
> The unused symbol KUC_FL_BLOCK has been removed.
> 
> Signed-off-by: frank zago <fzago at cray.com>
> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6245
> Reviewed-on: http://review.whamcloud.com/14270
> Reviewed-by: Nathan Rutman <nathan.rutman at seagate.com>
> Reviewed-by: James Simmons <uja.ornl at yahoo.com>
> Reviewed-by: Dmitry Eremin <dmitry.eremin at intel.com>
> Reviewed-by: John L. Hammond <john.hammond at intel.com>
> Reviewed-by: Oleg Drokin <oleg.drokin at intel.com>

Note, your subject is the most difficult to deal with, as you didn't put
the 'v2' before each patch, just some of them, so you can't sort them in
an email client and I have to hand-edit them to get this to apply
properly :(

Please don't do that again...



More information about the lustre-devel mailing list