This is kinda late but better than never.
This 10th edition of FOSDEM was a blast again. Got to see back good friends and meet new people.
This year was a bit special too because we happened to have a dedicated room for Mono thanks to the work of Ruben and Stéphane.
It was even more special for me since I also gave a talk about ParallelFx, your favorite parallel toolkit under Mono. Thanks to the work of Andrius, we have a complete and high quality video coverage of the day and Ruben has actually nicely summed up all the different links to each presentation on his blog.
All talks were great and you have no excuse for not watching all of them. On a personal side and related to ParallelFx, I recommend Alan talk on MonoTorrent (especially the part on threading) and Stéphane talk about Mono.Simd. I also really enjoyed Jim Purbrick talk on Second Life.
See you next year!
- Press My Buttons !
That was interesting… Good job.
Off topic: being also French, I’m sensible to English mispronunciations you’ve made (your English is still definitely better than the average French guy, mind you). You may already be aware of some of them, but just in case, I thought you might want to take some mental notes of what follows…
Each = you pronounce it « etch », it’s more like « itch »
Whole = you shouldn’t pronounce the W, it’s more like « hole » (at first, I actually thought you were saying « as a wall » when describing the image processing)
Promise = the « i » part should the pronounced the same as in « this », as opposed to « bike » (ie: « prom-is », not « prom-ahys »)
Notice = same as above
API = Ey Pee Aye
Anyway, back on topic… I’ll see if I can use ParallelFx in my own little app (I create Bitmaps pixel by pixel, so that sounds like a good candidate). Monocore users shouldn’t notice any performance difference, right? And are ParallelFx and unsafe code supposed to work well together?
PS: and when I said « sensible », I of course meant « sensitive ».
Mono-core user shouldn’t technically see any difference. In practice, there is still some overhead introduced by the whole scheduler thing but since the pixel processing takes so much time it’s barely noticeable.
Any kind of code, unsafe or not, works provided you take care of securing your shared state access if any.