On 2007-Apr-22 16:39:58 -0700, Howard Su <howard0su_at_gmail.com> wrote: >1. System wide global readonly page which will help on these syscalls: > gethostname,getdomainname,uname > help on importing sysenter as syscall entry point!! > >2. Per process Readonly page. (change will still through standard syscall) > help on the syscalls: > getuid, geteuid, getpid,getgid, getegid, getpgrp, I do not believe that these syscalls are called frequently enough that improving their efficiency will be measurable anywhere other than microbenchmarks that specifically measure their speed. I had a quick look through syscall.h and didn't see any syscalls that were both used often and were amenable to this approach. Before spending much efford on implementing this shared-page approach, I would suggest that you instrument syscall() to count the number of syscalls by type see if any heavily used syscalls can be implemented using this approach. The comment was made elsewhere "if it's easy to do, do it anyway, even if there's no measurable benefit". I would strongly disagree with this comment. Any code that is added to FreeBSD requires ongoing effort to maintain it - even if it's just waiting longer for the system to compile. Special casing some system calls means that those system calls need special regression tests to ensure that they haven't been broken somehow. Unless there is some benefit, then don't bother making the change. FreeBSD does appear to have higher syscall overheads than (eg) Linux. The best solution is to work on reducing this overhead in general (trap handling and syscall(), rather than identifying a small subset of syscalls and bypassing the syscall overhead for them. -- Peter Jeremy
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:09 UTC