This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: About JSON output generated by "bench-malloc-thread"
- From: Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>
- To: Francesco <francesco dot montorsi at gmail dot com>
- Cc: libc-help <libc-help at sourceware dot org>
- Date: Thu, 1 Feb 2018 21:25:04 +0530
- Subject: Re: About JSON output generated by "bench-malloc-thread"
- Authentication-results: sourceware.org; auth=none
- References: <CAKW0qigAOSW0CxkB==OuXBT4OZSkr_cggKcA0waZ+Sc6VG2pZA@mail.gmail.com> <CAAHN_R3WMJ_eMNZLoi6LZ+qqG9yrfdi=wjHUys_E+vjgWH7ocg@mail.gmail.com> <CAKW0qiiyEW4qhU7mAXuX=J+Ru6FZPxZU7cPBmye+a1-Ex3zk3A@mail.gmail.com> <CAAHN_R2R5Ec1trfrUOSmh4aXjtehSh8g18UdTSqhwm71x4N9Hw@mail.gmail.com> <CAKW0qijQ-UY6vOR3Xgh7_ukJmcvtXmCXcXa3-5DAb3iTniQuRw@mail.gmail.com>
On 1 February 2018 at 20:38, Francesco <francesco.montorsi@gmail.com> wrote:
> Do you think it's better to change the benchmark utility to generate a JSON
> that complies with existing JSON schema or rather write a new schema for
> that utility?
The schema and parser script should change to adapt to the benchmark
output. If the differences between the standard benchout schema and
malloc schema are minimal then just edit the standard schema.
Otherwise create a new parser script and schema for malloc.
> Actually I already transferred copyright to FSF for a patch I contributed to
> coreutils a while ago (several years ago actually)... not sure if that's
> enough
IIRC the FSF agreement is for specific projects, so you may have
signed the assignment only for coreutils and you may have to sign a
separate one for glibc. The friendly FSF clerks at assign@gnu.org
will be able to answer that question more comprehensively.
Siddhesh
--
http://siddhesh.in