[PATCH 1/1 v2] include/uapi/linux/sockios.h: mark SIOCRTMSG unused

IOCTL SIOCRTMSG does nothing but return EINVAL. So comment it as unused. SIOCRTMSG is only used in: * net/ipv4/af_inet.c * include/uapi/linux/sockios.h inet_ioctl calls ip_rt_ioctl. ip_rt_ioctl only handles SIOCADDRT and SIOCDELRT and returns -EINVAL otherwise. Signed-off-by: Heinrich

[RFD] cgroup: thread granularity support for cpu controller

Hello, This email is to restart the discussion around the thread granularity support for cgroup cpu controller, which got lost around the following message. http://thread.gmane.org/gmane.linux.kernel/2021959/focus=14454 While the previous discussion didn't reach a conclusion, it uncovered the

Re: [RFC PATCH 1/3] getcpu_cache system call: cache CPU number of running thread

- On Jan 5, 2016, at 12:31 PM, Mathieu Desnoyers mathieu.desnoy...@efficios.com wrote: > - On Jan 5, 2016, at 7:04 AM, Will Deacon will.dea...@arm.com wrote: > >> Hi Mathieu, >> >> On Tue, Jan 05, 2016 at 02:01:58AM -0500, Mathieu Desnoyers wrote: >>> Expose a new system call allowing

Re: lazytime implementation questions

Hi, On Mon 04-01-16 17:22:19, Dave Chinner wrote: > I've been looking at implementing the lazytime mount option for XFS, > and I'm struggling to work out what it is supposed to mean. > > AFAICT, on ext4, lazytime means that pure timestamp updates are not > journalled and they are only ever

Re: [RFC PATCH 1/3] getcpu_cache system call: cache CPU number of running thread

- On Jan 5, 2016, at 7:04 AM, Will Deacon will.dea...@arm.com wrote: > Hi Mathieu, > > On Tue, Jan 05, 2016 at 02:01:58AM -0500, Mathieu Desnoyers wrote: >> Expose a new system call allowing threads to register userspace memory >> areas where to store the CPU number on which the calling

Re: [RFC PATCH 1/3] getcpu_cache system call: cache CPU number of running thread

On Tue, Jan 05, 2016 at 05:31:45PM +, Mathieu Desnoyers wrote: > For instance, an application could create a linked list or hash map > of thread control structures, which could contain the current CPU > number of each thread. A dispatch thread could then traverse or > lookup this structure to

Re: [RFC PATCH 1/3] getcpu_cache system call: cache CPU number of running thread

- On Jan 5, 2016, at 12:40 PM, Russell King - ARM Linux li...@arm.linux.org.uk wrote: > On Tue, Jan 05, 2016 at 05:31:45PM +, Mathieu Desnoyers wrote: >> For instance, an application could create a linked list or hash map >> of thread control structures, which could contain the current

Re: CGroup Namespaces (v9)

On Mon, Jan 04, 2016 at 06:53:08PM -0600, Serge E. Hallyn wrote: > Ok, please hold off on this, there is another locking question i need to look > into :( With my v2 of patch 3 this is resolved, thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a

Re: [PATCH v2 10/14] serial: pic32_uart: Add PIC32 UART driver

On 12/20/2015 09:14 AM, Andy Shevchenko wrote: > On Tue, Dec 15, 2015 at 12:42 AM, Joshua Henderson > wrote: >> From: Andrei Pistirica >> >> This adds UART and a serial console driver for Microchip PIC32 class >> devices. >> >>

Re: [PATCH RFC] vhost: basic device IOTLB support

On 01/05/2016 11:18 AM, Yang Zhang wrote: > On 2016/1/4 14:22, Jason Wang wrote: >> >> >> On 01/04/2016 09:39 AM, Yang Zhang wrote: >>> On 2015/12/31 15:13, Jason Wang wrote: This patch tries to implement an device IOTLB for vhost. This could be used with for co-operation with

Re: [RFC PATCH 1/3] getcpu_cache system call: cache CPU number of running thread

On Tue, Jan 05, 2016 at 10:34:04PM +, Mathieu Desnoyers wrote: > - On Jan 5, 2016, at 4:47 PM, Paul E. McKenney paul...@linux.vnet.ibm.com > wrote: > > > On Tue, Jan 05, 2016 at 05:40:18PM +, Russell King - ARM Linux wrote: > >> On Tue, Jan 05, 2016 at 05:31:45PM +, Mathieu

Re: [RFC PATCH 1/3] getcpu_cache system call: cache CPU number of running thread

- On Jan 5, 2016, at 4:47 PM, Paul E. McKenney paul...@linux.vnet.ibm.com wrote: > On Tue, Jan 05, 2016 at 05:40:18PM +, Russell King - ARM Linux wrote: >> On Tue, Jan 05, 2016 at 05:31:45PM +, Mathieu Desnoyers wrote: >> > For instance, an application could create a linked list or

Re: [PATCH v2 10/14] serial: pic32_uart: Add PIC32 UART driver

> +#define PIC32_SDEV_NAME "ttyS" > +#define PIC32_SDEV_MAJOR TTY_MAJOR > +#define PIC32_SDEV_MINOR 64 No. Same goes for you as every one of the forty other people a year who try and claim their console is ttyS. If it's not an 8250 it isn't. ttyS is the 8250, use dynamic

Re: [PATCH 1/1 v2] include/uapi/linux/sockios.h: mark SIOCRTMSG unused

From: Heinrich Schuchardt Date: Tue, 5 Jan 2016 10:12:49 +0100 > IOCTL SIOCRTMSG does nothing but return EINVAL. > > So comment it as unused. > > SIOCRTMSG is only used in: > * net/ipv4/af_inet.c > * include/uapi/linux/sockios.h > > inet_ioctl calls ip_rt_ioctl. >

Re: [RFC PATCH 1/3] getcpu_cache system call: cache CPU number of running thread

On Tue, Jan 05, 2016 at 05:40:18PM +, Russell King - ARM Linux wrote: > On Tue, Jan 05, 2016 at 05:31:45PM +, Mathieu Desnoyers wrote: > > For instance, an application could create a linked list or hash map > > of thread control structures, which could contain the current CPU > > number of

Re: lazytime implementation questions

On Tue, Jan 05, 2016 at 06:36:04PM +0100, Jan Kara wrote: > Hi, > > On Mon 04-01-16 17:22:19, Dave Chinner wrote: > > I've been looking at implementing the lazytime mount option for XFS, > > and I'm struggling to work out what it is supposed to mean. > > > > AFAICT, on ext4, lazytime means

Re: [RFC PATCH 1/3] getcpu_cache system call: cache CPU number of running thread

Hi Mathieu, On Tue, Jan 05, 2016 at 02:01:58AM -0500, Mathieu Desnoyers wrote: > Expose a new system call allowing threads to register userspace memory > areas where to store the CPU number on which the calling thread is > running. Scheduler migration sets the TIF_NOTIFY_RESUME flag on the >

[PATCH 3/8 v3] cgroup: introduce cgroup namespaces

Introduce the ability to create new cgroup namespace. The newly created cgroup namespace remembers the cgroup of the process at the point of creation of the cgroup namespace (referred as cgroupns-root). The main purpose of cgroup namespace is to virtualize the contents of /proc/self/cgroup file.