HumanMedia;678603 Wrote: > > > All of these current tweaks are also based around the TT3 default core > process priorities. >
Yep that's correct. Though "current" tweaks are no tweaks, how I'd define them. It's just a different parametrization of one out of many other modifications. Similar to buffer value changes, though a bit more complex. HumanMedia;678603 Wrote: > > Im wondering if there could be a far better 'chord' of base process > priorities to tweak around? > You're invited to contribute that ""far better"" 'chord'. ;) I'm currently at a stage asking myself: "What more do I want? It's all there." When it comes to the process of how to identify certain settings: The logic that's been applied is putting potentially rather important processes/interrupts high and rather less important processes low. This is the starting point. (pretty much in line with the overal TT modification principle) What many of those processes and interrupts do is roughly indicated/described in the TT-code or you can look it up in the Linux environment or via Google. That'll give you at least some idea where to put this or that parameter. If a particular change of a single parameter has an impact or not doesn't really matter in the beginning. To speed things up you just put all potentially unimportant settings to lower values and rather important ones you line up in the upper range. If you don't do the rough grouping first it would take forever to get to results. And getting to results in a quite efficient way is the only thing what counts. Logitech had applied a similar logic when chosen their prio profile. Logitech though were facing the challenge to find the best compromise to avoid lockups or slowdowns of this or that process/function. To them it's more important to have the display and touchpad working smoothly. That's what the customer will see. On standard Linux kernels you'll find a CFS scheduler (Complete Fair Scheduler)in place. That one makes sure that a normal PC works smooth (fair) under all conditions. A realtime kernel is intentially all but "fair". There's no other OS which has a realtime kernel functionality built in like a rt-linux kernel. rt-kernels are ususally used for industrial realtime purposes. For a "fad" PClike system like the Touch, a modern 3.x CFS kernel might have been the better choice for Logitech. Though, I'm more than happy that there is an rt-kernel inside. Back to the tuning. The final finetuning of the prio mod - the cream on the cake - what's been discussed over here recently is more or less a trial and error excercise (prio Bingo). Nobody is able to look that deep into the code and kernel to figure out exactly how things exactly work together. It's really more about approximation and luck to find the best settings. SBGK's been the only one seriously supporting this excercise. Thx a lot for contributing your findings. Though as you can see from the continous changes that are currently being applied, the Bingo game is full in progress . It's all but stable yet. Nothing I would release to the public at this stage. That's why I've decided not to launch TT4.0 before Christmas. Enjoy your holidays. Merry Christmas. Cheers -- soundcheck ::: ' Touch Toolbox 3.0 and more' (http://soundcheck-audio.blogspot.com) ::: by soundcheck ------------------------------------------------------------------------ soundcheck's Profile: http://forums.slimdevices.com/member.php?userid=34383 View this thread: http://forums.slimdevices.com/showthread.php?t=91322 _______________________________________________ audiophiles mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/audiophiles
