Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1573317

Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

From Andy Lutomirski <luto@amacapital.net>
Newsgroups linux.kernel
Subject Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp
Date 2017-02-03 19:00 +0100
Message-ID <t6Qjp-4OT-31@gated-at.bofh.it> (permalink)
References <t6O7V-3sD-25@gated-at.bofh.it> <t6O7V-3sD-23@gated-at.bofh.it> <t6PdE-4aP-25@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Fri, Feb 3, 2017 at 8:42 AM, Hoeun Ryu <hoeun.ryu@gmail.com> wrote:
> On Sat, Feb 4, 2017 at 12:39 AM, Michal Hocko <mhocko@kernel.org> wrote:
>> On Sat 04-02-17 00:30:05, Hoeun Ryu wrote:
>>>  Using virtually mapped stack, kernel stacks are allocated via vmalloc.
>>> In the current implementation, two stacks per cpu can be cached when
>>> tasks are freed and the cached stacks are used again in task duplications.
>>> but the array for the cached stacks is statically allocated by per-cpu api.
>>>  In this new implementation, the array for the cached stacks are dynamically
>>> allocted and freed by cpu hotplug callbacks and the cached stacks are freed
>>> when cpu is down. setup for cpu hotplug is established in fork_init().
>>
>> Why do we want this? I can see that the follow up patch makes the number
>> configurable but the changelog doesn't describe the motivation for that.
>> Which workload would benefit from a higher value?
>>
>
> The key difference of this implementation, the cached stacks for a cpu
> is freed when a cpu is down.
> so the cached stacks are no longer wasted.
> In the current implementation, the cached stacks for a cpu still
> remain on the system when a cpu is down.
> I think we could imagine what if a machine has many cpus and someone
> wants to have bigger size of stack caches.

Then how about just registering a simple hotplug hook to free the
stacks without worrying about freeing the tiny array as well?

--Andy

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp Hoeun Ryu <hoeun.ryu@gmail.com> - 2017-02-03 16:40 +0100
  Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped  stacks using cpuhp Michal Hocko <mhocko@kernel.org> - 2017-02-03 16:40 +0100
    Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped  stacks using cpuhp Hoeun Ryu <hoeun.ryu@gmail.com> - 2017-02-03 17:50 +0100
      Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped  stacks using cpuhp Michal Hocko <mhocko@kernel.org> - 2017-02-03 18:20 +0100
      Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped  stacks using cpuhp Andy Lutomirski <luto@amacapital.net> - 2017-02-03 19:00 +0100
        Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped  stacks using cpuhp Hoeun Ryu <hoeun.ryu@gmail.com> - 2017-02-04 03:10 +0100
          Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped  stacks using cpuhp Michal Hocko <mhocko@kernel.org> - 2017-02-05 11:20 +0100
            Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped  stacks using cpuhp Hoeun Ryu <hoeun.ryu@gmail.com> - 2017-02-05 14:30 +0100

csiph-web