OS internals (for nerds only)

%3CLINGO-SUB%20id%3D%22lingo-sub-865809%22%20slang%3D%22en-US%22%3EOS%20internals%20(for%20nerds%20only)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-865809%22%20slang%3D%22en-US%22%3EContinuous%20innovation%20in%20the%20core%20operating%20system%20has%20enabled%20new%20scenarios%20that%20are%20key%20to%20securing%2C%20operating%20and%20reducing%20costs%20across%20your%20datacenter.%20Hear%20directly%20from%20the%20operating%20system%20architects%20on%20how%20they%20approach%20and%20design%20the%20technology%20behind%20features%20such%20as%20memory%20partitions%2C%20developing%20a%20modern%20filesystem%2C%20and%20GPU%20virtualization.%20In%20this%20session%20you%E2%80%99ll%20be%20the%20first%20to%20learn%20about%20what%E2%80%99s%20new%20in%20our%20technology.%20It%E2%80%99s%20a%20session%20you%20won%E2%80%99t%20want%20to%20miss!%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-865809%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBRK3166%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1007438%22%20slang%3D%22en-US%22%3ERE%3A%20OS%20internals%20(for%20nerds%20only)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1007438%22%20slang%3D%22en-US%22%3EAgree%20with%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F451408%22%20target%3D%22_blank%22%3E%40scottarbeit%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-994340%22%20slang%3D%22en-US%22%3ERE%3A%20OS%20internals%20(for%20nerds%20only)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-994340%22%20slang%3D%22en-US%22%3EThe%20content%20is%20amazing%2C%20thank%20you.%20AND%20someone%20should%20re-edit%20this%20video%20and%20make%20sure%20that%20we're%20seeing%20the%20computer%20screen%20during%20demos.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-993547%22%20slang%3D%22en-US%22%3ERE%3A%20OS%20internals%20(for%20nerds%20only)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-993547%22%20slang%3D%22en-US%22%3EA%20question%20regarding%20hot%20patching%3A%20What%20if%20an%20app%20relies%20on%20the%20same%20behavior%20of%20the%20method%20every%20time%20it's%20called%3F%20Say%20it%20does%20something%20like%3A%20var%20color1%20%3D%20GetColor()%3B%20%2F%2F%20returns%20red%20%2F%2F%20meanwhile%20hot%20patch%20happens%20var%20color2%20%3D%20GetColor()%3B%20%2F%2F%20returns%20green%20if%20(color1%20!%3D%20color2)%20%2F%2F%20Crash%20Both%20versions%20of%20GetColor%20work%20perfectly%20fine%2C%20but%20not%20when%20swapped%20during%20the%20lifetime%20of%20the%20app%2C%20making%20this%20virtually%20impossible%20to%20catch%20during%20testing.%20You'll%20probably%20not%20write%20exactly%20this%20kind%20of%20code%2C%20but%20I%20can%20imagine%20there%20are%20a%20lots%20and%20lots%20of%20possibilities%20to%20cause%20instability%20here.%20How%20did%20you%20solve%20that%3F%20Or%20is%20it%20not%20possible%20to%20solve%20this%20problem%3F%20And%20if%20not%20solved%2C%20how%20can%20you%20do%20it%20with%20enough%20confidence%20to%20not%20break%20things%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-993545%22%20slang%3D%22en-US%22%3ERE%3A%20OS%20internals%20(for%20nerds%20only)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-993545%22%20slang%3D%22en-US%22%3EA%20question%20regarding%20hot%20patching%3A%20What%20if%20an%20app%20relies%20on%20the%20same%20behavior%20of%20the%20method%20every%20time%20it's%20called%3F%20Say%20it%20does%20something%20like%3A%20var%20color1%20%3D%20GetColor()%3B%20%2F%2F%20returns%20red%20%2F%2F%20meanwhile%20hot%20patch%20happens%20var%20color2%20%3D%20GetColor()%3B%20%2F%2F%20returns%20green%20if%20(color1%20!%3D%20color2)%20%2F%2F%20Crash%20Both%20versions%20of%20GetColor%20work%20perfectly%20fine%2C%20but%20not%20when%20swapped%20during%20the%20lifetime%20of%20the%20app%2C%20making%20this%20virtually%20impossible%20to%20catch%20during%20testing.%20You'll%20probably%20not%20write%20exactly%20this%20kind%20of%20code%2C%20but%20I%20can%20imagine%20there%20are%20a%20lots%20and%20lots%20of%20possibilities%20to%20cause%20instability%20here.%20How%20did%20you%20solve%20that%3F%20Or%20is%20it%20not%20possible%20to%20solve%20this%20problem%3F%20And%20if%20not%20solved%2C%20how%20can%20you%20do%20it%20with%20enough%20confidence%20to%20not%20break%20things%3F%3C%2FLINGO-BODY%3E
Highlighted
Community Manager
Continuous innovation in the core operating system has enabled new scenarios that are key to securing, operating and reducing costs across your datacenter. Hear directly from the operating system architects on how they approach and design the technology behind features such as memory partitions, developing a modern filesystem, and GPU virtualization. In this session you’ll be the first to learn about what’s new in our technology. It’s a session you won’t want to miss!
4 Replies
Highlighted
A question regarding hot patching: What if an app relies on the same behavior of the method every time it's called? Say it does something like: var color1 = GetColor(); // returns red // meanwhile hot patch happens var color2 = GetColor(); // returns green if (color1 != color2) // Crash Both versions of GetColor work perfectly fine, but not when swapped during the lifetime of the app, making this virtually impossible to catch during testing. You'll probably not write exactly this kind of code, but I can imagine there are a lots and lots of possibilities to cause instability here. How did you solve that? Or is it not possible to solve this problem? And if not solved, how can you do it with enough confidence to not break things?
Highlighted
A question regarding hot patching: What if an app relies on the same behavior of the method every time it's called? Say it does something like: var color1 = GetColor(); // returns red // meanwhile hot patch happens var color2 = GetColor(); // returns green if (color1 != color2) // Crash Both versions of GetColor work perfectly fine, but not when swapped during the lifetime of the app, making this virtually impossible to catch during testing. You'll probably not write exactly this kind of code, but I can imagine there are a lots and lots of possibilities to cause instability here. How did you solve that? Or is it not possible to solve this problem? And if not solved, how can you do it with enough confidence to not break things?
Highlighted
The content is amazing, thank you. AND someone should re-edit this video and make sure that we're seeing the computer screen during demos.
Highlighted
Agree with @scottarbeit

View this session in the session catalog

View session