Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
@aaronsgiles Regarding the scheduler changes I mentioned, I figure I should probably fully understand the code before trying to optimize it. With that in mind, do you recall why (it seems) suspended executing devices are appended to the end of the executing list?
I ask since it seems it would allow for ditching a bit of logic in the core scheduler::timeslice() loop. Not much, granted, but Model 1 is a pathological case that would benefit from shaving off as many cycles from it as possible, having 6+ executing devices and a 500kHz timer.
Erm, I don't remember anymore? Maybe for the case where the disabled CPU gets enabled during that timeslice. I'd have to review the code a bit more and think on it.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
