Re: [2.6 patch] make CONFIG_SECCOMP default to n

>i was profiling the scheduler on x86 and noticed some overhead related 
>to SECCOMP, and indeed, SECCOMP runs disable_tsc() at _every_ 
>context-switch:

Does this also apply to processes not having changed into seccomp mode yet?


Jan Engelhardt
-- 
| Software Engineer and Linux/Unix Network Administrator
| Alphagate Systems, http://alphagate.hopto.org/
| jengelh's site, http://jengelh.hopto.org/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [2.6 patch] make CONFIG_SECCOMP default to n
  - From: Adrian Bunk <[email protected]>

Prev by Date: [PATCH] abstract type/size specification for assembly
Next by Date: Re: [PATCH] exec: Only allow a threaded init to exec from the thread_group_leader
Previous by thread: [2.6 patch] make CONFIG_SECCOMP default to n
Next by thread: CBD Compressed Block Device, New embedded block device
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]