Re: New Metrics to measure Load average

[sena seneviratne]

Hi Andrew,
Hi Nagar,

Thanks for your reply and for your time.

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 my question in the post was about performance testing after the 
changes being done.

--2) Now about the tests
--As I have documented all this yet need to perform some standard tests for 
the sake of completion.
--What tests should I carry out to prove that the system is still intact?
--
--Please tell me whether the below is correct?

--(a) As suggested by the http://kernel-perf.sourceforge.net/ the lmbench 
and re-aim-7 test packages can be used to test the ----performance of the 
kernel before making changes and after. (Not done as yet)

--(-b) Further tests have been carried out to check the response time of 
short tasks before making changes and after making --changes. The results 
indicated that there was no difference in the response time after 
introducing the changes to the kernel (done)

---(c) Thereafter the tests have been carried out to check the runtime of 
long tasks before and after making changes. The results of the tests 
revealed that there is no change in reported runtime in both occasions.(done)


Thanks
Sena Seneviratne
Computer Engineering Lab
School of Electrical and Information Engineering
Sydney University
Australia



At 10:04 AM 6/17/2006 -0700, you wrote:
> On Fri, 16 Jun 2006 21:46:08 +0530
> Balbir Singh <balbir@xxxxxxxxxx> wrote:
>
> > I think it is easier to make the changes to be per-task and then in
> > user-space account all information for the user (using the per-task data).
>
> Yes please try to do this.  There are all sorts of ways in which we could
> combine these stats on behalf of a particular application scenario.  Each
> scheme involves some sort of data loss, so each application needs new code
> to get the information which _it_ wants.
>
> We really should work on presenting the relevant information to userspace
> in a complete, efficient and un-post-processed manner so that
> application-specific userspace code can combine it in the manner which it
> desires.
>
> Balbir's new code (in -mm) is supposed to be the basis of _all_ new
> per-task accounting, so you should look at what additional information is
> needed and then find a way to transport it to userspace via Balbir's
> proposed framework, thanks.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/