> As for the utility of the benchmarks, come on. I know there are people
> on this list who write kernel code (hmm, I seem to recall somebody
> on here who does a lot of work on networking drivers...) and they
> may find it useful to get these kinds of measurements to see if
> changes have improved
>> Is a port of lmbench considered a modified benchmark?
>> I understand you cannot publish results saying it´s the output
>> of lmbench if you changed the bechmark, but only because you
>> used a ported one...?
>>
>> Funny in any case.
>
> you're also not allowed to publish partial results. the
> Is a port of lmbench considered a modified benchmark?
> I understand you cannot publish results saying it´s the output
> of lmbench if you changed the bechmark, but only because you
> used a ported one...?
>
> Funny in any case.
you're also not allowed to publish partial results. they have
rea
Is a port of lmbench considered a modified benchmark?
I understand you cannot publish results saying it´s the output
of lmbench if you changed the bechmark, but only because you
used a ported one...?
Funny in any case.
On Sat, Mar 22, 2008 at 12:18 PM, hiro <[EMAIL PROTECTED]> wrote:
> Perhaps th
Perhaps the copyright owner just wanted to make fun of intellectual property;)
> On Fri, Mar 21, 2008 at 10:51 AM, erik quanstrom <[EMAIL PROTECTED]> wrote:
> > > As I note in the README, lmbench's license carries the additional
> > > restriction that you cannot publish results from modified benchmarks,
> > > so keep your results to yourself.
> >
> > doesn't generating unp
On Fri, Mar 21, 2008 at 10:51 AM, erik quanstrom <[EMAIL PROTECTED]> wrote:
> > As I note in the README, lmbench's license carries the additional
> > restriction that you cannot publish results from modified benchmarks,
> > so keep your results to yourself.
>
> doesn't generating unpublishable r
> As I note in the README, lmbench's license carries the additional
> restriction that you cannot publish results from modified benchmarks,
> so keep your results to yourself.
doesn't generating unpublishable results defeat the purpose of a benchmark?
- erik
I've just finished porting what we thought were the 8 most useful
benchmarks from the lmbench v.2 suite to run natively in Plan 9. The
benchmarks are:
bw_file_rd: Measure file read bandwidth
bw_mem: Measure memory bandwidth for a several different operations
bw_pipe: Measure pipe bandwidth
bw_tcp:
