Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1445978
| From | Tejun Heo <tj@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC 02/18] cgroup_pids: track maximum pids |
| Date | 2016-07-19 03:10 +0200 |
| Message-ID | <rWrHP-5yJ-5@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <rJG1X-2jr-17@gated-at.bofh.it> <rJHr3-3m2-1@gated-at.bofh.it> <rJHAK-3pk-21@gated-at.bofh.it> <rJHKp-3sH-13@gated-at.bofh.it> <rW0HD-5da-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sun, Jul 17, 2016 at 08:11:31PM +0000, Topi Miettinen wrote: > On 06/13/16 21:33, Tejun Heo wrote: > > Hello, > > > > On Mon, Jun 13, 2016 at 09:29:32PM +0000, Topi Miettinen wrote: > >> I used fork callback as I don't want to lower the watermark in all cases > >> where the charge can be lowered, so I'd update the watermark only when > >> the fork really happens. > > > > I don't think that would make a noticeable difference. That's where > > we decide whether to grant fork or not after all and thus where the > > actual usage is. > > I tried using only charge functions, but then the result was too low. > With fork callback, the result was as expected. Can you please elaborate in more details? Thanks. -- tejun
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [RFC 02/18] cgroup_pids: track maximum pids Topi Miettinen <toiwoton@gmail.com> - 2016-07-17 22:20 +0200
Re: [RFC 02/18] cgroup_pids: track maximum pids Tejun Heo <tj@kernel.org> - 2016-07-19 03:10 +0200
Re: [RFC 02/18] cgroup_pids: track maximum pids Topi Miettinen <toiwoton@gmail.com> - 2016-07-19 19:00 +0200
Re: [RFC 02/18] cgroup_pids: track maximum pids Tejun Heo <tj@kernel.org> - 2016-07-19 20:20 +0200
csiph-web