public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Florian Weimer <fweimer@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>,
	Joseph Myers <joseph@codesourcery.com>,
	Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH] tst: Provide test for getrusage
Date: Mon, 22 Mar 2021 12:29:44 +0100	[thread overview]
Message-ID: <20210322122944.5bfa014e@jawa> (raw)
In-Reply-To: <87sg4toiin.fsf@igel.home>

[-- Attachment #1: Type: text/plain, Size: 722 bytes --]

Hi Andreas,

> On Mär 17 2021, Lukasz Majewski wrote:
> 
> > Maybe you (or anybody else from the community) have a better idea
> > on how to force the process to be "running" (active) for some time?
> >  
> 
> You don't get real-time scheduling on Unix.  You always have to
> account for a process stalling for an arbitrary amount of time.
> 
> Andreas.
> 

I'm just looking for ideas on how to reliably test getrusage.
Do you have any ideas?


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-03-22 11:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 10:42 Lukasz Majewski
2021-03-15 10:55 ` Andreas Schwab
2021-03-15 13:56   ` Lukasz Majewski
2021-03-17 16:04     ` Lukasz Majewski
2021-03-17 16:24       ` Andreas Schwab
2021-03-22 11:29         ` Lukasz Majewski [this message]
2021-03-22 19:47 ` Adhemerval Zanella

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=20210322122944.5bfa014e@jawa \
    --to=lukma@denx.de \
    --cc=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@linux-m68k.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).