[systemd-devel] [PATCHSET RE-RESEND] update unified hierarchy support

2016-03-25 Thread Tejun Heo
immediately to root. This means that pid to unit lookup may return a slice if the session or service unit the pid belonged to is already gone. Three patches are attached addressing each of the above. Thanks! -- tejun >From 278a39f0a8fa34cd899c6a08e76626c987a4713e Mon Sep 17 00:00:00 2001

[systemd-devel] [PATCHSET RESEND] update unified hierarchy support

2016-03-25 Thread Tejun Heo
(bounced for not being subscribed, resending...) Hello, Unified hierarchy is available on the 4.5 kernel but there have been several updates. 1. The __DEVEL__sane_behavior flag is gone. Unified hierarchy is now available as "cgroup2" filesystem type with its own super magic number. 2.

Re: [systemd-devel] [PATCH 1/4] cgroups: support for MemoryAndSwapLimit= setting

2013-10-10 Thread Tejun Heo
(cc'ing Johannes and quoting the whole body for context) Hey, guys. On Thu, Oct 10, 2013 at 10:28:16AM -0400, Tejun Heo wrote: > Hello, > > On Thu, Oct 10, 2013 at 04:03:20PM +0200, Lennart Poettering wrote: > > For example MemorySoftLimit is something we supported previou

Re: [systemd-devel] [PATCH 1/4] cgroups: support for MemoryAndSwapLimit= setting

2013-10-10 Thread Tejun Heo
Hello, On Thu, Oct 10, 2013 at 04:03:20PM +0200, Lennart Poettering wrote: > For example MemorySoftLimit is something we supported previously, but > which I recently removed because Tejun Heo (the kernel cgroup > maintainer, added to CC) suggested that the attribute wouldn't conti

Re: [systemd-devel] [HEADSUP] cgroup changes

2013-06-24 Thread Tejun Heo
Hello, On Mon, Jun 24, 2013 at 4:38 PM, Andy Lutomirski wrote: > Now I'm confused. I thought that support for multiple hierarchies was > going away. Is it here to stay after all? It is going to be deprecated but also stay around for quite a while. That said, I didn' t mean to use multiple hier

Re: [systemd-devel] [HEADSUP] cgroup changes

2013-06-24 Thread Tejun Heo
Hello, Andy. On Mon, Jun 24, 2013 at 04:27:17PM -0700, Andy Lutomirski wrote: > I guess what I'm trying to say here is that many systems will rather > fundamentally use systemd. Admins of those systems should still have > access to a reasonably large subset of cgroup functionality. If the > sing

Re: [systemd-devel] [HEADSUP] cgroup changes

2013-06-24 Thread Tejun Heo
Hello, On Mon, Jun 24, 2013 at 04:01:07PM -0700, Andy Lutomirski wrote: > So what is cgroup for? That is, what's the goal for what the new API > should be able to do? It is a for controlling and distributing resources. That part doesn't change. It's just not built to be used directly by indivi

Re: [systemd-devel] [HEADSUP] cgroup changes

2013-06-24 Thread Tejun Heo
Hello, On Mon, Jun 24, 2013 at 12:24:38PM -0700, Andy Lutomirski wrote: > Because more things are becoming per cpu without the option of moving > of per-cpu things on behalf of one cpu to another cpu. RCU is a nice > exception. Hmm... but in most cases it's per-cpu on the same cpu that initiated

Re: [systemd-devel] [HEADSUP] cgroup changes

2013-06-24 Thread Tejun Heo
Hello, Andy. On Mon, Jun 24, 2013 at 11:49:05AM -0700, Andy Lutomirski wrote: > > I have an idea where it should be headed in the long term but am not > > sure about short-term solution. Given that the only sort wide-spread > > use case is virt kthreads, maybe it just needs to be special cased fo

Re: [systemd-devel] [HEADSUP] cgroup changes

2013-06-24 Thread Tejun Heo
Hello, On Mon, Jun 24, 2013 at 03:27:15PM +0200, Lennart Poettering wrote: > On Sat, 22.06.13 15:19, Andy Lutomirski ([email protected]) wrote: > > > 1. I put all the entire world into a separate, highly constrained > > cgroup. My real-time code runs outside that cgroup. This seems to > > exa

Re: [systemd-devel] [HEADSUP] cgroup changes

2013-06-24 Thread Tejun Heo
Hello, On Mon, Jun 24, 2013 at 02:39:53PM +0100, Daniel P. Berrange wrote: > On Mon, Jun 24, 2013 at 03:27:15PM +0200, Lennart Poettering wrote: > > On Sat, 22.06.13 15:19, Andy Lutomirski ([email protected]) wrote: > > > > > 1. I put all the entire world into a separate, highly constrained > >