This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Benchmark for sem_timedwait v1.1
- From: OndÅej BÃlka <neleai at seznam dot cz>
- To: Siddhesh Poyarekar <siddhesh at redhat dot com>
- Cc: Roland McGrath <roland at hack dot frob dot com>, libc-alpha at sourceware dot org
- Date: Fri, 21 Feb 2014 20:26:56 +0100
- Subject: Re: Benchmark for sem_timedwait v1.1
- Authentication-results: sourceware.org; auth=none
- References: <20140211172324 dot GA31923 at domone dot podge> <20140211172720 dot 52ABB7445F at topped-with-meat dot com> <20140211184530 dot GB32451 at domone dot podge> <20140211204751 dot GA17236 at domone dot podge> <20140213102200 dot GA8107 at spoyarek dot pnq dot redhat dot com> <20140216152649 dot GA10444 at domone dot podge> <20140217050742 dot GC17663 at spoyarek dot pnq dot redhat dot com> <20140217101900 dot GA16967 at domone dot podge> <20140217103551 dot GF27461 at spoyarek dot pnq dot redhat dot com>
On Mon, Feb 17, 2014 at 04:05:51PM +0530, Siddhesh Poyarekar wrote:
> On Mon, Feb 17, 2014 at 11:19:00AM +0100, OndÅej BÃlka wrote:
> >
> > So test-skeleton is apparently ok. If it is not then you should fix that
> > first.
> >
>
> Those are all the string tests I ported from string/*. I haven't
> changed them yet because they have a very different output format and
> hence, won't fit into the generic benchmark skeleton yet. I should
> probably elaborate on my request: if all your benchmark does is print
> out timing information for inputs, then it should be adapted to use
> bench-skeleton.c. If there are other parameters you wish to capture
> in the output, then pretty much anything goes, altough it would be
> nice if a framework was written around them to reduce code
> duplication, which means use test-skeleton.c until you/I/someone-else
> comes up with something nicer.
>
There are no sensible inputs. There may be different usage patterns to
measure which may involve spawning threads which is out of bench-skeleton scope.