From: Pavel Machek <pavel@ucw.cz>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, mhocko@suse.cz,
minchan@kernel.org, anton@enomsg.org, akpm@linux-foundation.org
Subject: Re: [PATCH] vmpressure: implement strict mode
Date: Mon, 1 Jul 2013 10:51:03 +0200 [thread overview]
Message-ID: <20130701085103.GA19798@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20130625175129.7c0d79e1@redhat.com>
Hi!
> diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
> index ddf4f93..3c589cf 100644
> --- a/Documentation/cgroups/memory.txt
> +++ b/Documentation/cgroups/memory.txt
> @@ -807,12 +807,14 @@ register a notification, an application must:
>
> - create an eventfd using eventfd(2);
> - open memory.pressure_level;
> -- write string like "<event_fd> <fd of memory.pressure_level> <level>"
> +- write string like "<event_fd> <fd of memory.pressure_level> <level> [strict]"
> to cgroup.event_control.
>
This is.. pretty strange interface. Would it be cleaner to do ioctl()?
New syscall?
> @@ -303,22 +307,33 @@ int vmpressure_register_event(struct cgroup *cg, struct cftype *cft,
> {
> struct vmpressure *vmpr = cg_to_vmpressure(cg);
> struct vmpressure_event *ev;
> + bool smode = false;
> + const char *p;
> int level;
>
> for (level = 0; level < VMPRESSURE_NUM_LEVELS; level++) {
> - if (!strcmp(vmpressure_str_levels[level], args))
> + p = vmpressure_str_levels[level];
> + if (!strncmp(p, args, strlen(p)))
> break;
> }
>
> if (level >= VMPRESSURE_NUM_LEVELS)
> return -EINVAL;
>
> + p = strchr(args, ' ');
> + if (p) {
> + if (strncmp(++p, "strict", 6))
> + return -EINVAL;
> + smode = true;
> + }
> +
This looks like something for bash, not for kernel :-(.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2013-07-01 8:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 21:51 Luiz Capitulino
2013-06-26 0:28 ` Kyungmin Park
2013-06-26 1:12 ` Hyunhee Kim
2013-06-26 3:20 ` Luiz Capitulino
2013-06-26 4:03 ` Anton Vorontsov
2013-06-26 13:32 ` Luiz Capitulino
2013-06-26 7:50 ` Minchan Kim
2013-06-26 7:59 ` Michal Hocko
2013-06-26 8:20 ` Minchan Kim
2013-06-26 13:44 ` Luiz Capitulino
2013-06-26 18:00 ` Anton Vorontsov
2013-06-26 8:08 ` Michal Hocko
2013-06-26 13:45 ` Luiz Capitulino
2013-07-01 8:51 ` Pavel Machek [this message]
2013-07-02 15:06 ` Luiz Capitulino
2013-07-02 19:47 ` Pavel Machek
2013-07-02 21:55 ` Luiz Capitulino
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=20130701085103.GA19798@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=anton@enomsg.org \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=minchan@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
all inboxes | Powered by JetHome®