From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/4] lmbench: memsize: increase delay for slow FPGAs
Date: Tue, 18 May 2021 08:38:59 +0200 [thread overview]
Message-ID: <20210518063859.GJ2506@scaer> (raw)
In-Reply-To: <0c486431-d2fb-d7e7-0c35-9d419b31b48a@synopsys.com>
vineet, All,
On 2021-05-17 21:53 +0000, Vineet Gupta spake thusly:
> On 5/17/21 1:09 PM, Yann E. MORIN wrote:
> >
> >> OK
> >> ---
> > This triple-dash line is the usual git marker to end the actual commit
> > log, so everything below was dropped when applying the patch with git-am.
> > I've fixed that, and applied to master, thanks.
> Yep I'm aware of that and sorry - there's no easy way to "underline"
> stuff in a patch :-)
Oh yes, there _is_. ;-)
> > However, I wonder how relevant lmbench is nowadays. Indeed, there has
> > been zero activity on lmbench source code since June 2009, almost 12
> > years ago now...
> Depends on who you ask. I think it is still relevant for embedded
> platforms.? Especially when doing new CPU and/or ISA bringup - former we
> tend to do regularly at Synopsys it gives you a great "snapshot" of
> performance of 2 systems: old and new. And this is true starting from
> fork/shell latency to memory latency and bandwidth tests which are still
> pretty smart for something written so long ago.
Ah, yes, that makes sense, indeed.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2021-05-18 6:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 18:00 [Buildroot] [PATCH v3 0/4] Updates for ARC, LMBench Vineet Gupta
2021-05-10 18:00 ` [Buildroot] [PATCH v3 1/4] ARC: config: explicit'ify -mcpu for cpu selection Vineet Gupta
2021-05-17 19:24 ` Yann E. MORIN
2021-05-10 18:00 ` [Buildroot] [PATCH v2 2/3] lmbench: increase memsize delay for slow FPGAs Vineet Gupta
2021-05-10 18:00 ` [Buildroot] [PATCH v3 2/4] lmbench: memsize: increase " Vineet Gupta
2021-05-17 20:09 ` Yann E. MORIN
2021-05-17 21:53 ` Vineet Gupta
2021-05-18 6:38 ` Yann E. MORIN [this message]
2021-05-20 8:41 ` Peter Korsgaard
2021-05-10 18:00 ` [Buildroot] [PATCH v3 3/4] lmbench: emulate --prefix to avoid scattering binaries all over Vineet Gupta
2021-05-10 20:09 ` Thomas Petazzoni
2021-05-10 20:22 ` Vineet Gupta
2021-05-17 16:59 ` Yann E. MORIN
2021-05-10 18:00 ` [Buildroot] [PATCH v3 4/4] lmbench: lat_rpc: fix stray pointer Vineet Gupta
2021-05-17 20:09 ` Yann E. MORIN
2021-05-20 8:41 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210518063859.GJ2506@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox