https://bugs.kde.org/show_bug.cgi?id=476887
--- Comment #10 from asom...@gmail.com ---
Thanks! I look forward to trying it out in the next release. BTW, aio_writev
and aio_readv can also be invoked from lio_listio. That syscall is a real can
of worms. However, I don't know of any programs that
https://bugs.kde.org/show_bug.cgi?id=476887
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=476887
--- Comment #8 from asom...@gmail.com ---
> plus this is wrong
> "aio_read() will read iocb->aio_nbytes from the buffer pointed to by
Oops. Thanks for spotting that. I've just opened a review to fix it.
--
You are receiving this mail because:
Y
https://bugs.kde.org/show_bug.cgi?id=476887
--- Comment #7 from Paul Floyd ---
Synchonising with aio_return shouldn't be too difficult. I'll do something
along the same lines as Darwin but without the global
'was_a_successful_aio_read' variable and I'll put everything in the aio_return
pre-syscal
https://bugs.kde.org/show_bug.cgi?id=476887
--- Comment #6 from asom...@gmail.com ---
Thanks for the quick work!
> async reads are more complicated since we can't use the post-syscall, we need
> something else to know when to mark the memory as initialized.
A conforming implementation of async_
https://bugs.kde.org/show_bug.cgi?id=476887
--- Comment #5 from Paul Floyd ---
I've made quite a few improvements, but there are a few things that I'm not
sure about.
First, a quick Valgrind syscall digression. For synchronous syscalls that read
and write memory, Valgrind will track pre- and pos
https://bugs.kde.org/show_bug.cgi?id=476887
--- Comment #4 from Paul Floyd ---
The aio code needs more work, but I'm getting close to having something working
for writev and readv.
paulf> LD_PRELOAD=obj/usr/home/paulf/build/src/amd64.amd64/tmp/lib/libc.so.7
/home/paulf/scratch/valgrind/vg-in-pla
https://bugs.kde.org/show_bug.cgi?id=476887
--- Comment #3 from Paul Floyd ---
Looking at the code, I did a quick and dirty job for aio_read and aio_write
which doesn't correctly check everything. I've mostly copied the Darwin
implementation. I should manage to do the vector versions this week.
https://bugs.kde.org/show_bug.cgi?id=476887
--- Comment #2 from asom...@gmail.com ---
Thanks for looking into this, @pjfloyd. Let me know if there's anything I can
do to help.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=476887
--- Comment #1 from Paul Floyd ---
It'll take me a little time to work out how the vector reads ans writes work.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=476887
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
Assignee|n...@valgrin
11 matches
Mail list logo
