RE: [Fault-injection-developer] Need for benchmarking

[Wang, S. <sta...@in...>]

We've download "lmbench". And it may help us :)

Stan

> -----Original Message-----
> From: Lynch, Rusty [mailto:rus...@in...]
> Sent: 2002=C4=EA12=D4=C216=C8=D5 11:54
> To: Zhuang, Louis; Gao, Kevin; 'Rusty Lynch';
> fau...@li...
> Subject: RE: [Fault-injection-developer] Need for benchmarking
>=20
>=20
> Does LTP contain a benchmarking tool?  We could definitely=20
> run it to make sure we didn't accidentally break something=20
> else in the kernel.
>=20
> BTW, do not overlook using STP on OSDL as a testing tool.
> It's easy to use and there are a bunch of machines waiting
> to be utilized.
>=20
> 	-rusty
>=20
> > -----Original Message-----
> > From: Zhuang, Louis [mailto:lou...@in...]
> > Sent: Sunday, December 15, 2002 4:45 PM
> > To: Gao, Kevin; 'Rusty Lynch';=20
> > fau...@li...
> > Subject: RE: [Fault-injection-developer] Need for benchmarking
> >=20
> >=20
> > Maybe we can use LTP to test performance.
> >=20
> > -----Original Message-----
> > From: Gao, Kevin [mailto:kev...@in...]
> > Sent: Monday, December 16, 2002 8:31 AM
> > To: 'Rusty Lynch'; fau...@li...
> > Subject: RE: [Fault-injection-developer] Need for benchmarking
> >=20
> > We can do some tiny program to test the time of MMIO read,
> > write operation in such situation:
> >=20
> > common kernel.
> > Kernel with our FITH, but no faultset.
> > Kernel with our FITH, but the address of faultset is not=20
> > associate with the
> > operation.
> > Kernel with our FITH, corresponding faultset but no action.
> > Kernel with our FITH, and injection corresponding fault into=20
> > the operation.
> >=20
> > Any other ideas?
> >=20
> > Kevin
> >=20
> >=20
> > -----Original Message-----
> > From: Rusty Lynch [mailto:ru...@li...]
> > Sent: 2002=C4=EA12=D4=C214=C8=D5 0:36
> > To: fau...@li...
> > Subject: [Fault-injection-developer] Need for benchmarking
> >=20
> >=20
> > We could use some standardized benchmarking to
> > periodically run on our code base to get a feel for how
> > much overhead our changes are adding.
> >=20
> > For example our current code adds a hook to the
> > page fault handler.  It would be really easy to thrash
> > the kernel with even the smallest of tweaks to that
> > code.
> >=20
> > Any idea's?  Kevin, have planned on putting something
> > together?
> >=20
> >     -rustyl
> >=20
> >=20
> > -------------------------------------------------------
> > This sf.net email is sponsored by:
> > With Great Power, Comes Great Responsibility
> > Learn to use your power at OSDN's High Performance Computing =
Channel
> > http://hpc.devchannel.org/
> > _______________________________________________
> > Fault-injection-developer mailing list
> > Fau...@li...
> >=20
> =
https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
> >=20
> >=20
> > -------------------------------------------------------
> > This sf.net email is sponsored by:
> > With Great Power, Comes Great Responsibility
> > Learn to use your power at OSDN's High Performance Computing =
Channel
> > http://hpc.devchannel.org/
> > _______________________________________________
> > Fault-injection-developer mailing list
> > Fau...@li...
> >=20
> =
https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
> >=20
> >=20
> > -------------------------------------------------------
> > This sf.net email is sponsored by:
> > With Great Power, Comes Great Responsibility=20
> > Learn to use your power at OSDN's High Performance Computing =
Channel
> > http://hpc.devchannel.org/
> > _______________________________________________
> > Fault-injection-developer mailing list
> > Fau...@li...
> >=20
> =
https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
> >=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility=20
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Fault-injection-developer mailing list
> Fau...@li...
> =
https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
>=20