From: Minchan Kim <minchan@kernel.org>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] vmevent: Implement greater-than attribute state and one-shot mode
Date: Wed, 02 May 2012 16:41:31 +0900 [thread overview]
Message-ID: <4FA0E52B.7000907@kernel.org> (raw)
In-Reply-To: <CAOJsxLHdy8pBCBmbYfiHL681Bd=p_XPXjJHgVKqhT9nYquAjOg@mail.gmail.com>
On 05/02/2012 03:57 PM, Pekka Enberg wrote:
> On Wed, May 2, 2012 at 8:04 AM, Minchan Kim <minchan@kernel.org> wrote:
>> I think hardest problem in low mem notification is how to define _lowmem situation_.
>> We all guys (server, desktop and embedded) should reach a conclusion on define lowmem situation
>> before progressing further implementation because each part can require different limits.
>> Hopefully, I want it.
>>
>> What is the best situation we can call it as "low memory"?
>
> Looking at real-world scenarios, it seems to be totally dependent on
> userspace policy.
That's why I insist on defining low memory state in user space, not kernel.
>
> On Wed, May 2, 2012 at 8:04 AM, Minchan Kim <minchan@kernel.org> wrote:
>> As a matter of fact, if we can define it well, I think even we don't neead vmevent ABI.
>> In my opinion, it's not easy to generalize each use-cases so we can pass it to user space and
>> just export low attributes of vmstat in kernel by vmevent.
>> Userspace program can determine low mem situation well on his environment with other vmstats
>> when notification happens. Of course, it has a drawback that userspace couples kernel's vmstat
>> but at least I think that's why we need vmevent for triggering event when we start watching carefully.
>
> Please keep in mind that VM events is not only about "low memory"
> notification. The ABI might be useful for other kinds of VM events as
> well.
Fully agreed but we should prove why such event is useful in real scenario before adding more features.
>
> --
> 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/ .
> Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>
--
Kind regards,
Minchan Kim
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-05-02 7:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 8:32 [PATCH v2 0/2] vmevent: Greater-than attribute + one-shot mode + a bugfix Anton Vorontsov
2012-04-18 8:33 ` [PATCH 1/2] vmevent: Should not grab mutex in the atomic context Anton Vorontsov
2012-04-18 20:01 ` Pekka Enberg
2012-04-18 8:35 ` [PATCH 2/2] vmevent: Implement greater-than attribute and one-shot mode Anton Vorontsov
2012-04-18 20:01 ` Pekka Enberg
2012-04-18 22:46 ` Anton Vorontsov
2012-04-19 5:42 ` Pekka Enberg
2012-04-19 16:29 ` [PATCH v3 " Anton Vorontsov
2012-05-01 13:18 ` [PATCH v4] vmevent: Implement greater-than attribute state " Anton Vorontsov
2012-05-01 21:04 ` Rik van Riel
2012-05-02 0:20 ` Anton Vorontsov
2012-05-02 1:20 ` KOSAKI Motohiro
2012-05-02 3:31 ` Anton Vorontsov
2012-05-02 3:50 ` Anton Vorontsov
2012-05-02 5:04 ` Minchan Kim
2012-05-02 6:46 ` leonid.moiseichuk
2012-05-02 6:57 ` Pekka Enberg
2012-05-02 7:41 ` Minchan Kim [this message]
2012-05-02 6:51 ` Pekka Enberg
2012-05-03 10:52 ` Pekka Enberg
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=4FA0E52B.7000907@kernel.org \
--to=minchan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).