From: sena seneviratne <auntvini@cel.usyd.edu.au>
To: balbir@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, arjan@infradead.org
Subject: Fwd: Re: New Metrics to measure Load average
Date: Sat, 04 Oct 2008 00:22:58 +1000 [thread overview]
Message-ID: <5.1.1.5.2.20081004001904.022c2ef8@brain.cel.usyd.edu.au> (raw)
Dear Balbir Singh,
This is one of the e-mails probably the last.
By this time I have finshed 2.4.19 kernel.
Thanks
Sena Seneviratne
Computer Engineering Lab
School of Electrical and Information Engineering
Sydney University
Australia
>Date: Tue, 20 Jun 2006 19:43:36 +1000
>To: balbir@in.ibm.com
>From: sena seneviratne <auntvini@sedal.usyd.edu.au>
>Subject: Re: New Metrics to measure Load average
>
>Dear Balbir Singh,
>
>Thanks for your reply and for your time.
>
>Then I will have to transfer from 2.4.18 to 2.6.18
>
>Ok Balbir I will do that.
>
>
>Kind regards
>Sena Seneviratne
>Computer Engineering Lab
>School of Electrical and Information Engineering
>Sydney University
>Australia
>
>
>
>At 02:29 PM 6/20/2006 +0530, you wrote:
>>sena seneviratne wrote:
>>>Dear Balbir Singh,
>>>Thanks for your valuable reply.
>>>Balbir It looks like that there is a general project where we all can
>>>incorporate our work.
>>
>>
>>Yes it is. It is currently in -mm and we hope that it makes it into
>>2.6.18. The folder Documentation/accounting contains all the necessary
>>details for you to build on top of delay stats.
>>
>>
>>>--How do you calculate disk load? Is it the
>>>---number of uninterruptible tasks in the system? Yes I started at that
>>>point
>>>
>>>Few years ago the few additions I have explained, have been implemented
>>>in linux 2.4.18 kernel at the Sydney Uni as part of a large research project.
>>>Also few years ago I have posted many posts about this topic to this
>>>forum. Few very experience hands were advising me in coding at that
>>>time. To prove this I have all the e-mails with me. Yet then I had not
>>>explained to this forum about the research project which involved
>>>prediction algorithm as then it had not been published.
>>>Thereafter few research papers have been published with regard to this.
>>>1 in US.
>>>Currently I am preparing the changes to a more recent linux patch. In
>>>fact this is not hard as I have already changed the previous linux 2.4.18.
>>
>>Please cc us when you post the patches.
>>
>>>Before coming to do research I had worked as a Senior software engineer
>>>in few companies and my last was LogicaCMG. Yet as far as the kernel
>>>programming is concerned I will ask for your comments and advice.
>>
>>Let us know if you need any help for coding on top of taskstats.
>>
>>>Thanks
>>>Sena Seneviratne
>>>Computer Engineering Lab
>>>School of Electrical and Information Engineering
>>>Sydney University
>>>Australia
next reply other threads:[~2008-10-04 0:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 14:22 sena seneviratne [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-06 20:55 sena seneviratne
2008-10-07 12:07 ` Balbir Singh
2008-10-08 13:47 ` sena seneviratne
[not found] <5.1.1.5.2.20060828105624.033aecc8@brain.sedal.usyd.edu.au>
[not found] ` <44F24DF6.3000001@bigpond.net.au>
2006-08-28 2:29 ` sena seneviratne
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=5.1.1.5.2.20081004001904.022c2ef8@brain.cel.usyd.edu.au \
--to=auntvini@cel.usyd.edu.au \
--cc=arjan@infradead.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.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®