Re: [PATCH] Documentation/memory-barriers: fix wrong comment in example

2016-02-20 Thread SeongJae Park
On Sun, Feb 21, 2016 at 4:57 AM, Paul E. McKenney wrote: > On Sat, Feb 20, 2016 at 03:01:08PM +0900, SeongJae Park wrote: >> There is wrong comment in example for compiler store omit behavior. It >> shows example of the problem and than problem solved version code. >> However, the comment in the

Re: [PATCH] Documentation/memory-barriers: fix wrong comment in example

2016-02-20 Thread Paul E. McKenney
On Sat, Feb 20, 2016 at 03:01:08PM +0900, SeongJae Park wrote: > There is wrong comment in example for compiler store omit behavior. It > shows example of the problem and than problem solved version code. > However, the comment in the solved version is still same with not solved > version. Fix th

[PATCH v5 0/3] init: add support to directly boot to a mapped device

2016-02-20 Thread Kees Cook
This is a resurrection of a patch series from a few years back, first brought to the dm maintainers in 2010. It creates a way to define dm devices on the kernel command line for systems that do not use an initramfs, or otherwise need a dm running before init starts. This has been used by Chrome OS

[PATCH v5 3/3] init: add support to directly boot to a mapped device

2016-02-20 Thread Kees Cook
This change adds a dm= kernel parameter modelled after the md= parameter from do_mounts_md. It allows for simple device-mapper targets to be configured at boot time for use early in the boot process (as the root device or otherwise). The format is as follows: dm="count name uuid|none ro|rw num-tab

[PATCH v5 2/3] dm: make mapped_device locking functions available

2016-02-20 Thread Kees Cook
For init to build a mapped_device, it must hold the appropriate locks, so move these to the common header. Signed-off-by: Kees Cook --- v5: first version of this specific patch in the series --- drivers/md/dm.h | 2 -- include/linux/device-mapper.h | 6 ++ 2 files changed, 6 in

[PATCH v5 1/3] dm: export a table+mapped device to the ioctl interface

2016-02-20 Thread Kees Cook
From: Will Drewry If a mapped device and table is configured without traversing the dm-ioctl interface (dm-fs-style), then it will not be bound to a name or uuid. This means that it will be inaccessible for userspace management and udev will be unhappy with the lack of a name or uuid. The functi

[PATCHv6 2/3] IB/core: added support to use rdma cgroup controller

2016-02-20 Thread Parav Pandit
Added support APIs for IB core to register/unregister every RDMA device with rdma cgroup for tracking verbs and hw resources. IB core registers with rdma cgroup controller and also defines resources that can be accounted. Added support APIs for uverbs layer to make use of rdma controller. Added uve

[PATCHv6 3/3] rdmacg: Added documentation for rdmacg

2016-02-20 Thread Parav Pandit
Added documentation for v1 and v2 version describing high level design and usage examples on using rdma controller. Signed-off-by: Parav Pandit --- Documentation/cgroup-v1/rdma.txt | 106 +++ Documentation/cgroup-v2.txt | 33 2 files changed

[PATCHv6 1/3] rdmacg: Added rdma cgroup controller

2016-02-20 Thread Parav Pandit
Added rdma cgroup controller that does accounting, limit enforcement on rdma/IB verbs and hw resources. Added rdma cgroup header file which defines its APIs to perform charing/uncharing functionality and device registration which will participate in controller functions of accounting and limit enf

[PATCHv6 0/3] rdmacg: IB/core: rdma controller support

2016-02-20 Thread Parav Pandit
Overview: Currently user space applications can easily take away all the rdma device specific resources such as AH, CQ, QP, MR etc. Due to which other applications in other cgroup or kernel space ULPs may not even get chance to allocate any rdma resources. This results into service unavailibility.