Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 319
    • Issues 319
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #1229
Closed
Open
Created Jan 25, 2010 by Trac@tracbot

cpu affinity cpuworker threads

v0.2.2.6-alpha on Debian Squeeze x86_64

On Blutmagie exit node I recently noticed all onionskin cpuworker threads always run on the same core as the main thread. Don't know if this is can be considered a bug, but it renders the Numcpu config option pretty useless.

Olaf

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ P COMMAND 25495 debian-t 20 0 987m 567m 27m R 95.7 14.3 11369:12 0 tor 7328 debian-t 20 0 987m 567m 27m S 2.7 14.3 15:04.47 0 tor 7330 debian-t 20 0 987m 567m 27m S 2.3 14.3 15:59.22 0 tor 1 root 20 0 10324 684 572 S 0.0 0.0 1:32.45 1 init [...]

[Automatically added by flyspray2trac: Operating System: Other Linux]

Trac:
Username: Falo

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking