linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: paul.szabo@sydney.edu.au
To: minchan@kernel.org, psz@maths.usyd.edu.au
Cc: 695182@bugs.debian.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] Subtract min_free_kbytes from dirtyable memory
Date: Fri, 25 Jan 2013 20:53:24 +1100	[thread overview]
Message-ID: <201301250953.r0P9rOSe012192@como.maths.usyd.edu.au> (raw)

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@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>

             reply	other threads:[~2013-01-25  9:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25  9:53 paul.szabo [this message]
2013-01-25 13:01 ` Bug#695182: " Ben Hutchings
2013-01-25 23:49   ` paul.szabo
2013-01-26  0:10     ` Ben Hutchings
2013-01-26  3:05       ` paul.szabo
2013-01-26  3:07       ` paul.szabo
2013-01-26  3:17         ` Ben Hutchings
2013-01-26  0:14     ` Jonathan Nieder
2013-01-26 15:43       ` Theodore Ts'o
2013-01-26  7:44   ` Bug#695182: " Jonathan Nieder
2013-01-26 20:23     ` paul.szabo
2013-01-28  6:23 ` Minchan Kim
  -- strict thread matches above, loose matches on Subject: below --
2013-01-21  3:15 paul.szabo
2013-01-21 17:49 ` Rik van Riel
2013-01-22 23:38 ` Andrew Morton
2013-01-23  1:49 ` Minchan Kim
2013-01-23  3:11   ` paul.szabo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201301250953.r0P9rOSe012192@como.maths.usyd.edu.au \
    --to=paul.szabo@sydney.edu.au \
    --cc=695182@bugs.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=psz@maths.usyd.edu.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox