patches are out, did I make it before freezing point?

Just posted patches that hopefully will be accepted. I not, I will have even more exciting work to do! :)
check them out:
git@gitorious.org:xenvnuma/linuxvnuma.git:v3
git@gitorious.org:xenvnuma/xenvnuma.git:v3

For sure, I feel so much comfortable with patches formatting.

I have to say that tremendous amount of experience I was able to accumulate since May of this year.
LinuxCon, XenProject Developers Summit, meeting my mentors in Edinburgh (they are really nice),
then meeting other people - Sarah Sharp and Greg K-H.
I know, the next year it will be more exciting, more challenges and more friends.

Ok, now I have to take of my job situation :)

Phew.. first some sleep

Dropped RFC tag for Xen vNUMA: https://git.gitorious.org/xenvnuma/xenvnuma_rfcdrop.git.
Next!

Nvidia! I need GeForce driver for 3.12 kernel! Do you need help? :)

Whew... :)

I can't believe that only three months ago I was selected for the program.
I worked on presentation slides for LinuxCon UK today. I have to admit - I like working on code much more that on slides :)

Anyways, I progress towards second patch submission, though rinsing the patchsets might take some time yet. But vNUMA feauture was freezed for Xen 4.4! So no rest after program is over, but actually I dont feel I really need it. I feel good about last changes in my code, I look at it without shruging my shoulders :)

Also, exciting enough is my attendance at GNU 30th celebration hackaton at MIT :) I will get prepared. Looking forwrad to meet Linux Foundation people and other hackers, as well as OPW participants!

repos has been moved to http://gitorious.org/xenvnuma/ by xen-devel community request.

After the program I will commit more time and post detailed program results...
I wish I would do it for another few months! But in any case, there is no way back and I will keep hacking. Makes me content.

Git repo

Lets get it rolling!  In a real self-hosted repo!
Ok, just dont hack me while I am asleep :)

---
No more :)

Patches rfc review

I have submitted my patches to xen-devel list both for Xen/toolstack and linux.
Looks like they are trashy :) I will have to clean them up and re-send once again.

I have got tons of comments from maintainers and now I will jump on them, sort them all out and fix/clean stuff. Looks like I also need a git tree.

I have spent good amount of time clenaning patches, applying them and compiling on each of the stages. As I get this experience, I think I will try to keep in mind the organization of patches as well.

Also I have signed up for some programming courser at coursera.org. I hope that i will learn from solving optimization tasks and would approach my NP-problem in a right way :)

I am really busy. 

I have days when I think I know how exactly solve everything :)

Sometime I go dark.

I hit an NP-problem with memory allocation. Because of the timing issue I have decided to avoid it and instead made it very simple, for now. I will sure have time to improve.. but still its NP-problem.

The code grows, I am pushing it hard so it will make to the xen-devel and lklm this week.

Huge work ahead of me on organizing patches, commenting them and formatting, rebasing and applying to the current trees. After the review, I will have to fix all errors or make changes and all over again :)

Well, in draft the whole project works, few bits there and there.

But every day I see more and more room for improvement and I also know what maintainters will tell me :)

But its ok, Id rather push it a bit and have the rest of the time for fixing and communicating.

The very-very important thing I have learned - prototyping!

I can now prototype some pieces of my tasks pretty quickly and this helps great deal. When dealing with a lot of code, this kind of modeling helps to see your algorithm very quick, test all corner cases (or most of them ;), debug and move back to the project efficiently.

So, as I am approaching official code submission, I'd better go off writing change list :)