Linux Container Development
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
To: Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	Balbir Singh
	<balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Subject: Re: [PATCH] Add a 'trigger' callback on struct cftype.
Date: Tue, 11 Mar 2008 19:21:46 +0300	[thread overview]
Message-ID: <47D6B19A.3080906@openvz.org> (raw)
In-Reply-To: <6599ad830803110916i1bbc7c7an2412c0facb3496ef-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Paul Menage wrote:
> On Tue, Mar 11, 2008 at 9:13 AM, Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org> wrote:
>> --- a/include/linux/cgroup.h
>>  +++ b/include/linux/cgroup.h
>>  @@ -243,7 +243,7 @@ struct cftype {
>>
>>          */
>>         int (*write_s64) (struct cgroup *cgrp, struct cftype *cft, s64 val);
>>
>>  -       void (*trigger) (struct cgroup *cgrp, unsigned int event);
>>  +       int (*trigger) (struct cgroup *cgrp, unsigned int event);
> 
> To be more name-compatible with the other read_X/write_X functions,
> how about write_void rather than trigger?

Because it's not a write actually, this is just some kick-up which came
from the user space. And the fact, that it is triggered via the sys_write
is just a VFS-based API constraints. Besides, if we ever have a binary 
API with cgroups, this trigger can be triggered :) via some other system
call, rather than write.

> Paul
> 

  parent reply	other threads:[~2008-03-11 16:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 15:21 [PATCH] Add a 'trigger' callback on struct cftype Pavel Emelyanov
     [not found] ` <47D6A36F.2080706-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-03-11 16:00   ` Paul Menage
     [not found]     ` <6599ad830803110900j7d47bd6eqf8747bdb704c9226-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-03-11 16:13       ` Pavel Emelyanov
     [not found]         ` <47D6AF98.4030204-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-03-11 16:16           ` Paul Menage
     [not found]             ` <6599ad830803110916i1bbc7c7an2412c0facb3496ef-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-03-11 16:21               ` Pavel Emelyanov [this message]
     [not found]                 ` <47D6B19A.3080906-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-03-13  9:37                   ` Pavel Emelyanov
     [not found]                     ` <47D8F5E9.5000203-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-03-13  9:41                       ` Paul Menage

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=47D6B19A.3080906@openvz.org \
    --to=xemul-gefaqzzx7r8dnm+yrofe0a@public.gmane.org \
    --cc=balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.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