> I think the best solution is to move the KAIO syscall;
> you should be using the dynamically linked (.so) version
> of the KAIO library, so moving the syscall number should
> work out OK. I'll post new patches on KAIO soon (today
> if possible). Also, I'm curious to hear your experiences
> with Sybase + KAIO.
i agree, moving the kaio syscalls would be the best solution.
but unfortunately, sybase-22.214.171.124 (the only one with aio support)
cannot use the new kaio-libs. they are using a somewhat outdated
version. if i remember right, the initialization failed.
if i'm on site (today evening), i will do some checks
and mail the result directly to ananth@xxxxxxxx
my experiences with kaio are good so far. i measured an improvement
of approx. 15% in my db-benchmarks (2 kaio-threads).
i'm using sybase-126.96.36.199 + rawio + kaio.