[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <201301250953.r0P9rOSe012192@como.maths.usyd.edu.au>
Date: Fri, 25 Jan 2013 20:53:24 +1100
From: paul.szabo@...ney.edu.au
To: minchan@...nel.org, psz@...hs.usyd.edu.au
Cc: 695182@...s.debian.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH] Subtract min_free_kbytes from dirtyable memory
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 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.
Thanks, Paul
Paul Szabo psz@...hs.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics University of Sydney Australia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists