Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3D73692E.6030100@goingware.com>
Date: Mon, 02 Sep 2002 09:35:42 -0400
From: "Michael D. Crawford" <crawford AT goingware DOT com>
Organization: GoingWare Inc. - Expert Software Development and Consulting
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.0.0) Gecko/20020622 Debian/1.0.0-0.woody.1
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Need Benchmark Stats
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Maybe it would be helpful to port some Linux validation test tools to Cygwin, 
then one could test both for correctness and speed.

There are a couple packages for testing Linux system calls:

http://ltp.sourceforge.net/
http://www.linuxbase.org/test/

 From what I read before, the Linux Standards Base has two suites, one for 
testing filesystem layout and the other for testing system call POSIX compliance.

So what I'm suggesting is that you use these tools to test that your emulated 
system calls work correctly.  I would imagine the tools can be gotten to report 
the time they take, so capture that in a file and test on a variety of 
configurations and post it on the website.

Mike
-- 
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
crawford AT goingware DOT com

      Tilting at Windmills for a Better Tomorrow.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/