All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: rsf@flying-dove.com, linux-kernel@vger.kernel.org
Subject: Re:  OLS2003 Performance BOF Proposals
Date: Sat, 08 Mar 2003 13:15:34 -0800	[thread overview]
Message-ID: <3E6A5D76.9090704@us.ibm.com> (raw)

> 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


             reply	other threads:[~2003-03-08 21:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-08 21:15 Nivedita Singhvi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-12 16:14 OLS2003 Performance BOF Proposals Sandra K Johnson
2003-03-08 18:51 Ruth Forester
2003-03-11  1:12 ` Craig Thomas

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=3E6A5D76.9090704@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rsf@flying-dove.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.