From: Anton Vorontsov <anton.vorontsov@linaro.org>
To: Pekka Enberg <penberg@kernel.org>
Cc: Leonid Moiseichuk <leonid.moiseichuk@nokia.com>,
John Stultz <john.stultz@linaro.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linaro-kernel@lists.linaro.org, patches@linaro.org
Subject: Re: [PATCH 2/2] vmevent: Implement greater-than attribute and one-shot mode
Date: Wed, 18 Apr 2012 15:46:32 -0700 [thread overview]
Message-ID: <20120418224629.GA22150@lizard> (raw)
In-Reply-To: <alpine.LFD.2.02.1204182259580.11868@tux.localdomain>
On Wed, Apr 18, 2012 at 11:01:02PM +0300, Pekka Enberg wrote:
> On Wed, 18 Apr 2012, Anton Vorontsov wrote:
> > This patch implements a new event type, it will trigger whenever a
> > value becomes greater than user-specified threshold, it complements
> > the 'less-then' trigger type.
> >
> > Also, let's implement the one-shot mode for the events, when set,
> > userspace will only receive one notification per crossing the
> > boundaries.
> >
> > Now when both LT and GT are set on the same level, the event type
> > works as a cross event type: it triggers whenever a value crosses
> > the threshold from a lesser values side to a greater values side,
> > and vice versa.
> >
> > We use the event types in an userspace low-memory killer: we get a
> > notification when memory becomes low, so we start freeing memory by
> > killing unneeded processes, and we get notification when memory hits
> > the threshold from another side, so we know that we freed enough of
> > memory.
> >
> > Signed-off-by: Anton Vorontsov <anton.vorontsov@linaro.org>
>
> Did you try vmevent-test with this patch? I'm seeing this:
Yep, with CONFIG_SWAP=n, and I had to a modify the test
since I saw the same thing, I believe. I'll try w/ the swap enabled,
and see how it goes. I think the vmevent-test.c needs some improvemnts
in general, but meanwhile...
> Physical pages: 109858
> read failed: Invalid argument
Can you send me the .config file that you used? Might be that
you have CONFIG_SWAP=n too?
Thanks!
--
Anton Vorontsov
Email: cbouatmailru@gmail.com
next prev parent reply other threads:[~2012-04-18 22:47 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 [this message]
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
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=20120418224629.GA22150@lizard \
--to=anton.vorontsov@linaro.org \
--cc=john.stultz@linaro.org \
--cc=leonid.moiseichuk@nokia.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=patches@linaro.org \
--cc=penberg@kernel.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).