linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: [PATCH v2 0/2] vmevent: Greater-than attribute + one-shot mode + a bugfix
Date: Wed, 18 Apr 2012 01:32:08 -0700	[thread overview]
Message-ID: <20120418083208.GA24904@lizard> (raw)

Hi all,

That's a respin of the previous patchset that tried to add a new
'cross' event type, which would trigger whenever value crosses a
user-specified threshold both ways, i.e. from a lesser values side
to a greater values side, and vice versa.

We use the event type 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.

There's also a fix for a bug that makes kernel upset about sleeping
in the atomic context.

Per Pekka's comments here comes v2. Changes:

- Added a one-shot mode plus a greater-than attribute, the two
  additions makes the equivalent of the cross-event type.
- In the bugfix patch I added some comments about implementation
  details of the lock-free logic. Also, in the previous version of
  the fix I forgot to remove 'struct mutex' form the
  'struct vmevent_watch', this is now cleaned up.

As usual, the patches are against

	git://github.com/penberg/linux.git vmevent/core

Thanks!

-- 
Anton Vorontsov
Email: cbouatmailru@gmail.com

             reply	other threads:[~2012-04-18  8:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18  8:32 Anton Vorontsov [this message]
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
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=20120418083208.GA24904@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).