search for: commit_s

The freeze rwsem is taken by sb_start_intwrite() and dropped during the commit_ or end_transaction(). In the async case, that happens in a worker thread. Tell lockdep the calling thread is releasing ownership of the rwsem and the async thread is picking it up. Josef and I worked out a more complicated solution that made the async commit thread join and potentially get a later transaction, but

Hi -- I''ve got a very strange error. I have an action called ''commit_input'' on a controller called ''SiteVisitController''. This definately exists, and is called from the functional test for it, and passes fine. My problem is with the form that is supposed to call this action. The form tag is: <%=

I''ve been working to try to improve the write-ahead log''s performance, and I found that the bottleneck addresses in the checksum items, especially when we want to make a random write on a large file, e.g a 4G file. Then a idea for this suggested by Chris is to use sub transaction ids and just to log the part of inode that had changed since either the last log commit or the last

...ching back to the synchronous execution ioloop afterwards and then destroying that via io_loop_destroy. This works but is probably not exactly how the existing interfaces were supposed to be used. error messages for synchronously committed transaction These are put onto the data stack by the commit_s subroutine which will hopefully (judging from the dict-code, this should work, too) be sufficient to enable them to survive until someone higher up in the callchain wants to look at them. Remarks on the Patch -------------------- Created against dovecot-1-2-cf3fe573a560. Applies cleanly to 1....