#24554: sched: Have per-scheduler type data in a channel_t -------------------------------------------------+------------------------- Reporter: dgoulet | Owner: (none) Type: enhancement | Status: | assigned Priority: Very High | Milestone: Tor: | unspecified Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: tor-sched, 034-triage-20180328, | Actual Points: 034-removed-20180328, tor-chan | Parent ID: #23993 | Points: Reviewer: | Sponsor: -------------------------------------------------+------------------------- Changes (by dgoulet):
* keywords: tor-sched, 034-triage-20180328, 034-removed-20180328 => tor- sched, 034-triage-20180328, 034-removed-20180328, tor-chan Comment: Branch `ticket24554_033_02` has all the things! Wow. It is way too big. It should be broken down into smaller pieces (tickets) and then properly tested. This should really go in tor because it will help greatly to reduce our technical debt around the scheduler subsystem. But also, one particular thing, is that it removes the heap memory allocation done for each channel at each KIST mainloop. Under pressure, this leads to memory fragmentation quite a bit, and it has been observed. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24554#comment:16> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs