Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory
On Fri, Jan 25, 2013 at 08:53:24PM +1100, paul.szabo@sydney.edu.au wrote:
> Dear Minchan,
>
> > So what's the effect for user?
> > ...
> > It seems you saw old kernel.
> > ...
> > Current kernel includes ...
> > So I think we don't need this patch.
>
> As I understand now, my patch is "right" and needed for older kernels;
> for newer kernels, the issue has been fixed in equivalent ways; it was
> an oversight that the change was not backported; and any justification
> you need, you can get from those "later better" patches.
I don't know your problem because you didn't write down your problem in
changelog. Anyway, If you want to apply it into older kernel,
please read Documentation/stable_kernel_rules.txt.
In summary,
1. Define your problem.
2. Apply your fix to see the problem goes away in older kernel.
3. If so, write the problem and effect in changelog
4. Send it to stable maintainers and mm maintainer
That's all.
>
> I asked:
>
> A question: what is the use or significance of vm_highmem_is_dirtyable?
> It seems odd that it would be used in setting limits or threshholds, but
> not used in decisions where to put dirty things. Is that so, is that as
> should be? What is the recommended setting of highmem_is_dirtyable?
>
> The silence is deafening. I guess highmem_is_dirtyable is an aberration.
I hope this helps you find primary reason of your problem.
git show 195cf453
>
> Thanks, Paul
>
> Paul Szabo psz@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
> School of Mathematics and Statistics University of Sydney Australia
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org";> email@kvack.org </a>
--
Kind regards,
Minchan Kim
Reply to: