mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Dan Malek <dan@embeddedalley.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Paul Menage <menage@google.com>
Subject: Re: [PATCH] Memory usage limit notification addition to memcg
Date: Thu, 16 Apr 2009 08:45:04 +0530	[thread overview]
Message-ID: <20090416031504.GC7082@balbir.in.ibm.com> (raw)
In-Reply-To: <9272A08E-4928-486D-84D3-4593300B017A@embeddedalley.com>

* Dan Malek <dan@embeddedalley.com> [2009-04-15 10:35:20]:

>
> On Apr 15, 2009, at 1:24 AM, Balbir Singh wrote:
>
>> Welcome! I've taken a cursory look at the patches, but I'll come back
>> with more review comments.
>
> I'm going to submit a new patch shortly, so let's wait and review that
> one.  Too many updates since the first time I sent it.
>

OK, I was going to advice using cgroupstats for notification.
cgroupstats builds on top of taskstats

Please see

1. Documentation/accounting/*
2. kernel/taskstats.c

getdelays.c (available under (1)) provides the user space application
to make use of taskstats and cgroupstats.

Using that will allow you to

1. Provide type information with every event (extensible)
2. Reuses existing well tested code in the form of genetlink and
netlink


>> ...   Could you point me to your
>> presentation/paper? I could not find the PDF at
>> http://www.celinuxforum.org/CelfPubWiki/ELC2009Presentations
>
> Apologies.  I just uploaded it now.  There was an hour of
> talking that goes along with that, which I hope will explain some
> of the points on the slides.  The video was recorded, I assume it
> will show up someplace, someday :-)
>

I was able to download it, Thanks!

-- 
	Balbir

  reply	other threads:[~2009-04-16  3:16 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 22:08 Dan Malek
2009-04-13 23:08 ` Andrew Morton
2009-04-13 23:45   ` Dan Malek
2009-04-13 23:54     ` Andrew Morton
2009-04-14  0:52       ` Dan Malek
2009-04-15  0:35 ` KAMEZAWA Hiroyuki
2009-04-15  2:34   ` Dan Malek
2009-04-15  2:58     ` KAMEZAWA Hiroyuki
2009-04-15  7:32       ` Dan Malek
2009-04-15  7:33         ` KAMEZAWA Hiroyuki
2009-04-15  8:24   ` Balbir Singh
2009-04-15 17:35     ` Dan Malek
2009-04-16  3:15       ` Balbir Singh [this message]
2009-07-07 20:25 ` [PATCH 0/1] " Vladislav Buzov
2009-07-07 20:25   ` [PATCH 1/1] " Vladislav Buzov
2009-07-08  0:56     ` KAMEZAWA Hiroyuki
2009-07-09  1:43       ` Vladislav D. Buzov
2009-07-13  0:52         ` KAMEZAWA Hiroyuki
2009-07-13 21:21           ` Vladislav D. Buzov
2009-07-13 22:15       ` Paul Menage
2009-07-14  1:00         ` Vladislav D. Buzov
2009-07-14  1:03           ` KAMEZAWA Hiroyuki
2009-07-14  1:43         ` KOSAKI Motohiro
2009-07-14 19:13           ` Dan Malek
2009-07-16 17:15             ` Balbir Singh
2009-07-16 18:16               ` Dan Malek
2009-07-17  2:33                 ` Balbir Singh
2009-07-15  6:02         ` Balbir Singh
2009-07-08  3:52     ` Balbir Singh
2009-07-10 18:01       ` Vladislav D. Buzov
2009-07-14  0:16   ` [PATCH 0/2] Memory usage limit notification feature (v3) Vladislav Buzov
2009-07-14  0:16     ` [PATCH 1/2] Resource usage threshold notification addition to res_counter (v3) Vladislav Buzov
2009-07-14  0:16       ` [PATCH 2/2] Memory usage limit notification addition to memcg (v3) Vladislav Buzov
2009-07-14  0:30       ` [PATCH 1/2] Resource usage threshold notification addition to res_counter (v3) KAMEZAWA Hiroyuki
2009-07-14  1:29         ` Vladislav D. Buzov
2009-07-14  1:45           ` KAMEZAWA Hiroyuki
2009-07-14  0:36       ` Paul Menage
2009-07-14  0:47         ` KAMEZAWA Hiroyuki
2009-07-14  0:20     ` [PATCH 0/2] Memory usage limit notification feature (v3) Paul Menage
2009-07-14  0:31       ` KOSAKI Motohiro

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=20090416031504.GC7082@balbir.in.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=dan@embeddedalley.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    /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®