public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Levent Serinol <lserinol@gmail.com>
To: Jay Lan <jlan@engr.sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
	pavel@ucw.cz, linux-kernel@vger.kernel.org,
	lse-tech@lists.sourceforge.net,
	Guillaume Thouvenin <guillaume.thouvenin@bull.net>,
	kaigai@ak.jp.nec.com, elsa-devel@lists.sourceforge.net,
	Erik Jacobson <erikj@subway.americas.sgi.com>,
	John Hesterberg <jh@sgi.com>
Subject: Re: [PATCH] per process I/O statistics for userspace
Date: Sat, 17 Sep 2005 20:36:00 +0300	[thread overview]
Message-ID: <2c1942a705091710363f463b18@mail.gmail.com> (raw)
In-Reply-To: <432890BA.5090907@engr.sgi.com>

Hi Andrew,

 What's your last decision about the patch ?

On 9/15/05, Jay Lan <jlan@engr.sgi.com> wrote:
> Andrew,
> 
> These data are used in CSA Accounting today and i believe ELSA
> intends to use them also.
> 
> Since PAGG is not in the tree, SGI have been offering our customers
> PAGG/JOB/CSA kernel code as either kernel patches at oss.sgi.com
> site or out-of-tree kernel modules today.
> 
> SGI intends to submit another solution for PAGG/JOB soon.
> 
> Once the future of PAGG/JOB becomes clear, we will know better how
> to integrate CSA and BSD accounting. We are not sitting on it.
> 
> Thanks,
>   - jay
> 
> 
> Andrew Morton wrote:
> > Levent Serinol <lserinol@gmail.com> wrote:
> >
> >>+int proc_pid_iostat(struct task_struct *task, char *buffer)
> >> +{
> >> +       return sprintf(buffer,"%llu %llu\n",task->rchar,task->wchar);
> >> +}
> >
> >
> > Those fields have been sitting there unused for months.  I'd like to hear
> > what the system accounting guys are intending to do with them before
> > proceeding, please.
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> 
> 


-- 

Stay out of the road, if you want to grow old. 
~ Pink Floyd ~.

  reply	other threads:[~2005-09-17 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-12 12:27 [PATCH] per process I/O statistics for userspace Levent Serinol
2005-09-14  9:23 ` Pavel Machek
2005-09-14 20:17   ` Levent Serinol
2005-09-14 20:24     ` Andrew Morton
2005-09-14 21:06       ` Jay Lan
2005-09-17 17:36         ` Levent Serinol [this message]
2005-09-17 20:58           ` Andrew Morton

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=2c1942a705091710363f463b18@mail.gmail.com \
    --to=lserinol@gmail.com \
    --cc=akpm@osdl.org \
    --cc=elsa-devel@lists.sourceforge.net \
    --cc=erikj@subway.americas.sgi.com \
    --cc=guillaume.thouvenin@bull.net \
    --cc=jh@sgi.com \
    --cc=jlan@engr.sgi.com \
    --cc=kaigai@ak.jp.nec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=pavel@ucw.cz \
    /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