通过

It Goes to Eleven and ... to the NT Insider!

  • 项目

Well - for anyone bored enough to track such things, I have been pretty slammed lately and haven't blogged anything. I have a bunch of stuff queued up though. Upcoming posts (in the next few days hopefully) are:

1. The Anatomy of a Context Switch

2. The Anatomy of an Interrupt

3. The Anatomy of a Rootkit

Also – the guys over at OSR were nice enough to ask me to write an article for them. It is going to be in the March/April edition of the Insider.

I am also looking for topics of interest to the community at large if anyone has suggestions – please send them my way. Thanks!

Comments

  • Anonymous
    April 29, 2008
    The comment has been removed

  • Anonymous
    May 05, 2008
    I like the way you think Eran! :D You are correct in your paranoia - that the compiler can/will be able to do stuff like this in the future. The key thing is to analyze the code in the worst case scenario where it gets inlined. This makes you future proof even if the compiler changes underneath you. In the case of the queued irp - queueing usually implies a locked operation of some type which will create a barrier in the code. Does that make sense at all? :) Thanks!

  • Anonymous
    October 30, 2008
    I just subscribed to your blog and I think it's great! You haven't written anything since May, but please, post something about the topics you mentioned here, I'd love to hear more about it...