# Re: \[RFC\]\[PATCH 1/2\] sched: Extended scheduler time slice

- From: Steven Rostedt \<rostedt@goodmis.org\>
- Date: 2025-02-02 22:29:26 
- List: linux-trace-kernel
- Page: https://ratatoskr.run/linux-trace-kernel/2025/02/2908801
- Thread: https://ratatoskr.run/linux-trace-kernel/2025/01/2908056/t.md

```text
On Sun, 2 Feb 2025 07:22:08 +0000
Matthew Wilcox [ref] wrote:

> On Sat, Feb 01, 2025 at 10:22:08PM -0500, Steven Rostedt wrote:
> > And before seeing Peter's use of yield(), I was reluctant to use it for
> > the very same reasons you mentioned above. In my test programs, I was
> > simply using getuid(), as that was one of the quickest syscalls.  
> 
> Is getuid() guaranteed to issue a syscall?  It feels like the kind of
> information that a tricksy libc could cache.  Traditionally, I think
> we've used getppid() as the canonical "very cheap syscall" as no layer
> can cache that information.

Maybe that was what I used. Can't remember. And I think I even open
coded it using syscall() to not even rely on glibc.

-- Steve
```
