About :: TODO :: Blog :: RSS :: Old blog :: Projects :: GIT :: Gallery :: Notes

Mon, 04 Dec 2006

Meanwhile on flat development side.


I completed to fill self-leveling floor in kitchen, bathroom and part of the hall - do not believe the advertisement, it does not self leveling, no matter how thick the layer is - one needs to level it during filling. Its nature is about the same as plaster, so it behaves exactly like it, but it is more fluid. I spent about an hour mixing and filling, and then about 3 hours to finally level it - get palette-knife and meter-by-meter stating to cut all non even parts, with some water oiling it becomes quite good.

Thinking some more about hinged ceiling I decided to implement second layer even although there are no long enough hangers - I will use parts of ceiling profiles with cut middle part to implement some kind of 'U' hangers - without middle part it is possible to level ceiling.

/devel/flat :: Link / Comments (0)

Multidimensional trie test has been completed.


It ran for almost two days and about 7.4 milliards of insert/search operations were completed in 1 million series. No crashes, no failed searches or inserts, no bugs. It's a win.
I start to combine netchannels and this algorithm so wildcards get supported.
Thus netchannels become extremely useful functionality for Linux network stack - it allows to create and test different network stacks in userspace or kernelspace, thus creating TOE engines without influence on core stack (since netchannels engine runs before core network protocol hooks are called), it allows to create very fast and scalable network filters and packet manipulation entities like NAT. Can you ever consider Linux system with one million netfilter rules? System with million of sockets is already quite hard to get.
I also have some plans to implement userspace network stack as a library and patch existing web server (likely lighttpd to work with it - it only requires one netchannel (wildcard of course), i.e. only one socket in existing notation, and socket and related structures like inodes and files allocation and freeing and related syscall overhead is quite major limiting factor in existing systems.
Other system usage include packet-socket-like interface - when userspace can select set of IP addressed to work with without main kernel stack - like BGP/OSPF daemons, TUN/TAP interface, VPN proxies and much more.

So there are plenty of interesting ideas, which I plan to sublimate my energy into...

/devel/networking :: Link / Comments (0)