From: Pekka Enberg <penberg@kernel.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: Anton Vorontsov <anton@enomsg.org>,
Hyunhee Kim <hyunhee.kim@samsung.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH] memcg: event control at vmpressure.
Date: Tue, 11 Jun 2013 16:13:18 +0300 [thread overview]
Message-ID: <CAOJsxLF8TCCLJWaNrydEatcYgj49ChBsNLJXpMaUTfRywUMm9w@mail.gmail.com> (raw)
In-Reply-To: <20130611062124.GA24031@dhcp22.suse.cz>
On Tue, Jun 11, 2013 at 9:21 AM, Michal Hocko <mhocko@suse.cz> wrote:
>> Or, if you still want the "one-shot"/"edge-triggered" events (which might
>> make perfect sense for medium and critical levels), then I'd propose to
>> add some additional flag when you register the event, so that the old
>> behaviour would be still available for those who need it. This approach I
>> think is the best one.
>
> Hmm, how would one-shot even differ from a single open, register, read
> and close?
Yup, one-shot probably doesn't make sense but edge-triggered does.
--
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>
prev parent reply other threads:[~2013-06-11 13:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 11:14 Hyunhee Kim
2013-06-10 14:09 ` Luiz Capitulino
2013-06-10 15:12 ` Michal Hocko
2013-06-11 0:17 ` Anton Vorontsov
2013-06-11 1:01 ` Kyungmin Park
2013-06-11 6:21 ` Michal Hocko
2013-06-11 8:49 ` [PATCH v2] " Hyunhee Kim
2013-06-11 12:59 ` Michal Hocko
2013-06-12 5:42 ` Hyunhee Kim
2013-06-12 13:09 ` Michal Hocko
2013-06-11 13:10 ` [PATCH] " Luiz Capitulino
2013-06-11 13:13 ` Pekka Enberg [this message]
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=CAOJsxLF8TCCLJWaNrydEatcYgj49ChBsNLJXpMaUTfRywUMm9w@mail.gmail.com \
--to=penberg@kernel.org \
--cc=anton@enomsg.org \
--cc=hyunhee.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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