Message-ID: <3E6A5D76.9090704@us.ibm.com>
Date: Sat, 08 Mar 2003 13:15:34 -0800
From: Nivedita Singhvi <niv@us.ibm.com>
Reply-To: niv@us.ibm.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
MIME-Version: 1.0
To: rsf@flying-dove.com, linux-kernel@vger.kernel.org
Subject: Re:  OLS2003 Performance BOF Proposals
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1933
Lines: 39

> I would very much appreciate comments (even one-liners) on any  
> community interest in these two OLS Performance BoF sessions.  I  
> believe the topics are dissimilar and relevant enough to justify both:

> PROPOSAL FOR LINUX BENCHMARK AUTOMATION
> This BOF will include a discussion on Linux benchmark automation. We  
> will discuss the features needed to provide an effective benchmark  
> automation process for Linux. This will include, defining the  
> configuration, input files, benchmark execution, output files, etc.  We  
> will also discuss the types of benchmarks that are tailored for rapid  
> execution and results analysis, for maximum development impact.
> 
> PROPOSAL FOR LINUX PERFORMANCE
> Linux changes occur very quickly in the open source community. There is  
> a strong need to quickly collect and share performance data and  
> analysis. However, there may be some instances where good, quality  
> performance data collection and analysis take longer than the short  
> turnaround required for maximum impact regarding newly released  
> patches. We plan to discuss the most effective methodology for  
> impacting Linux performance in a rapidly changing Linux open source  
> community environment.

While the first is fairly clear on what the content might be,
its not very clear what the second is referring to..At first
I figured they were going to be discussing techniques like
how to automate the benchmark process to make it faster
(which would overlap with the first, I imagine?), but if not,
is it going to be about which benchmarks to run etc? or how to
avoid benchmark legalese miseries that can make them a big
headache?? :)

thanks,
Nivedita

-
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/