[PATCH] mm:Add watermark slope for high mark

2017-11-24 Thread Peter Enderborg
When tuning the watermark_scale_factor to reduce stalls and compactions the high mark is also changed, it changed a bit too much. So this patch introduces a slope that can reduce this overhead a bit, or increase it if needed. Signed-off-by: Peter Enderborg --- Documentation/sysctl/vm.txt | 15 ++

Re: [PATCH] mm:Add watermark slope for high mark

2017-11-24 Thread Michal Hocko
On Fri 24-11-17 11:07:07, Peter Enderborg wrote: > When tuning the watermark_scale_factor to reduce stalls and compactions > the high mark is also changed, it changed a bit too much. So this > patch introduces a slope that can reduce this overhead a bit, or > increase it if needed. This doesn't ex

Re: [PATCH] mm:Add watermark slope for high mark

2017-11-24 Thread Vlastimil Babka
On 11/24/2017 11:14 AM, Michal Hocko wrote: > On Fri 24-11-17 11:07:07, Peter Enderborg wrote: >> When tuning the watermark_scale_factor to reduce stalls and compactions >> the high mark is also changed, it changed a bit too much. So this >> patch introduces a slope that can reduce this overhead a

Re: [PATCH] mm:Add watermark slope for high mark

2017-11-24 Thread peter enderborg
On 11/24/2017 11:15 AM, Vlastimil Babka wrote: > Agreed. Also if you send a patch adding userspace API or a tuning knob, > please CC linux-api mailing list (did that for this reply). > The cc-list is generated by get_maintainer.pl script. -- To unsubscribe from this list: send the line "unsubscrib

Re: [PATCH] mm:Add watermark slope for high mark

2017-11-24 Thread peter enderborg
On 11/24/2017 11:14 AM, Michal Hocko wrote: > On Fri 24-11-17 11:07:07, Peter Enderborg wrote: >> When tuning the watermark_scale_factor to reduce stalls and compactions >> the high mark is also changed, it changed a bit too much. So this >> patch introduces a slope that can reduce this overhead a

Re: [PATCH] mm:Add watermark slope for high mark

2017-11-24 Thread Michal Hocko
On Fri 24-11-17 14:12:56, peter enderborg wrote: > On 11/24/2017 11:14 AM, Michal Hocko wrote: > > On Fri 24-11-17 11:07:07, Peter Enderborg wrote: > >> When tuning the watermark_scale_factor to reduce stalls and compactions > >> the high mark is also changed, it changed a bit too much. So this > >

Re: [PATCH v5 11/11] intel_sgx: driver documentation

2017-11-24 Thread Jarkko Sakkinen
On Fri, Nov 17, 2017 at 01:43:10PM -0800, Darren Hart wrote: > This series will need to be updated per the comments received so far, as > well as with commit messages and a complete Cc list *per patch* giving > all required parties an opportunity to review. > > With respect to the obvious security

Re: [RFC] doc: add maintainer book

2017-11-24 Thread Dan Williams
On Tue, Nov 21, 2017 at 2:39 PM, Tobin C. Harding wrote: > There is currently very little documentation in the kernel on maintainer > level tasks. In particular there are no documents on creating pull > requests to submit to Linus. > > Quoting Greg Kroah-Hartman on LKML: > > Anyway, this actua

Re: [RFC] doc: add maintainer book

2017-11-24 Thread Tobin C. Harding
On Fri, Nov 24, 2017 at 11:02:49AM -0800, Dan Williams wrote: > On Tue, Nov 21, 2017 at 2:39 PM, Tobin C. Harding wrote: > > There is currently very little documentation in the kernel on maintainer > > level tasks. In particular there are no documents on creating pull > > requests to submit to Lin

[PATCH v2] doc: add maintainer book

2017-11-24 Thread Tobin C. Harding
There is currently very little documentation in the kernel on maintainer level tasks. In particular there are no documents on creating pull requests to submit to Linus. Quoting Greg Kroah-Hartman on LKML: Anyway, this actually came up at the kernel summit / maintainer meeting a few weeks

Re: [PATCH v2] doc: add maintainer book

2017-11-24 Thread Greg Kroah-Hartman
On Sat, Nov 25, 2017 at 08:44:19AM +1100, Tobin C. Harding wrote: > There is currently very little documentation in the kernel on maintainer > level tasks. In particular there are no documents on creating pull > requests to submit to Linus. > > Quoting Greg Kroah-Hartman on LKML: > > Anyway,