… | |
… | |
45 | Unlike the name component C<stamp> might indicate, it is also used for |
45 | Unlike the name component C<stamp> might indicate, it is also used for |
46 | time differences throughout libeio. |
46 | time differences throughout libeio. |
47 | |
47 | |
48 | =head2 FORK SUPPORT |
48 | =head2 FORK SUPPORT |
49 | |
49 | |
50 | Calling C<fork ()> is fully supported by this module - but you must not |
50 | Usage of pthreads in a program changes the semantics of fork |
51 | rely on this. It is currently implemented in these steps: |
51 | considerably. Specifically, only async-safe functions can be called after |
|
|
52 | fork. Libeio uses pthreads, so this applies, and makes using fork hard for |
|
|
53 | anything but relatively fork + exec uses. |
52 | |
54 | |
53 | 1. wait till all requests in "execute" state have been handled |
55 | This library only works in the process that initialised it: Forking is |
54 | (basically requests that are already handed over to the kernel). |
56 | fully supported, but using libeio in any other process than the one that |
55 | 2. fork |
57 | called C<eio_init> is not. |
56 | 3. in the parent, continue business as usual, done |
|
|
57 | 4. in the child, destroy all ready and pending requests and free the |
|
|
58 | memory used by the worker threads. This gives you a fully empty |
|
|
59 | libeio queue. |
|
|
60 | |
58 | |
61 | Note, however, since libeio does use threads, the above guarantee doesn't |
59 | You might get around by not I<using> libeio before (or after) forking in |
62 | cover your libc, for example, malloc and other libc functions are not |
60 | the parent, and using it in the child afterwards. You could also try to |
63 | fork-safe, so there is very little you can do after a fork, and in fact, |
61 | call the L<eio_init> function again in the child, which will brutally |
64 | the above might crash, and thus change. |
62 | reinitialise all data structures, which isn't POSIX conformant, but |
|
|
63 | typically works. |
|
|
64 | |
|
|
65 | Otherwise, the only recommendation you should follow is: treat fork code |
|
|
66 | the same way you treat signal handlers, and only ever call C<eio_init> in |
|
|
67 | the process that uses it, and only once ever. |
65 | |
68 | |
66 | =head1 INITIALISATION/INTEGRATION |
69 | =head1 INITIALISATION/INTEGRATION |
67 | |
70 | |
68 | Before you can call any eio functions you first have to initialise the |
71 | Before you can call any eio functions you first have to initialise the |
69 | library. The library integrates into any event loop, but can also be used |
72 | library. The library integrates into any event loop, but can also be used |
… | |
… | |
78 | This function initialises the library. On success it returns C<0>, on |
81 | This function initialises the library. On success it returns C<0>, on |
79 | failure it returns C<-1> and sets C<errno> appropriately. |
82 | failure it returns C<-1> and sets C<errno> appropriately. |
80 | |
83 | |
81 | It accepts two function pointers specifying callbacks as argument, both of |
84 | It accepts two function pointers specifying callbacks as argument, both of |
82 | which can be C<0>, in which case the callback isn't called. |
85 | which can be C<0>, in which case the callback isn't called. |
|
|
86 | |
|
|
87 | There is currently no way to change these callbacks later, or to |
|
|
88 | "uninitialise" the library again. |
83 | |
89 | |
84 | =item want_poll callback |
90 | =item want_poll callback |
85 | |
91 | |
86 | The C<want_poll> callback is invoked whenever libeio wants attention (i.e. |
92 | The C<want_poll> callback is invoked whenever libeio wants attention (i.e. |
87 | it wants to be polled by calling C<eio_poll>). It is "edge-triggered", |
93 | it wants to be polled by calling C<eio_poll>). It is "edge-triggered", |
… | |
… | |
131 | |
137 | |
132 | If C<eio_poll ()> is configured to not handle all results in one go |
138 | If C<eio_poll ()> is configured to not handle all results in one go |
133 | (i.e. it returns C<-1>) then you should start an idle watcher that calls |
139 | (i.e. it returns C<-1>) then you should start an idle watcher that calls |
134 | C<eio_poll> until it returns something C<!= -1>. |
140 | C<eio_poll> until it returns something C<!= -1>. |
135 | |
141 | |
136 | A full-featured conenctor between libeio and libev would look as follows |
142 | A full-featured connector between libeio and libev would look as follows |
137 | (if C<eio_poll> is handling all requests, it can of course be simplified a |
143 | (if C<eio_poll> is handling all requests, it can of course be simplified a |
138 | lot by removing the idle watcher logic): |
144 | lot by removing the idle watcher logic): |
139 | |
145 | |
140 | static struct ev_loop *loop; |
146 | static struct ev_loop *loop; |
141 | static ev_idle repeat_watcher; |
147 | static ev_idle repeat_watcher; |
… | |
… | |
276 | |
282 | |
277 | =over 4 |
283 | =over 4 |
278 | |
284 | |
279 | =item eio_cancel (eio_req *req) |
285 | =item eio_cancel (eio_req *req) |
280 | |
286 | |
281 | Cancel the request (and all it's subrequests). If the request is currently |
287 | Cancel the request (and all its subrequests). If the request is currently |
282 | executing it might still continue to execute, and in other cases it might |
288 | executing it might still continue to execute, and in other cases it might |
283 | still take a while till the request is cancelled. |
289 | still take a while till the request is cancelled. |
284 | |
290 | |
285 | Even if cancelled, the finish callback will still be invoked - the |
291 | Even if cancelled, the finish callback will still be invoked - the |
286 | callbacks of all cancellable requests need to check whether the request |
292 | callbacks of all cancellable requests need to check whether the request |
… | |
… | |
405 | free (target); |
411 | free (target); |
406 | } |
412 | } |
407 | |
413 | |
408 | =item eio_realpath (const char *path, int pri, eio_cb cb, void *data) |
414 | =item eio_realpath (const char *path, int pri, eio_cb cb, void *data) |
409 | |
415 | |
410 | Similar to the realpath libc function, but unlike that one, result is |
416 | Similar to the realpath libc function, but unlike that one, C<< |
411 | C<-1> on failure and the length of the returned path in C<ptr2> (which is |
417 | req->result >> is C<-1> on failure. On success, the result is the length |
412 | not 0-terminated) - this is similar to readlink. |
418 | of the returned path in C<ptr2> (which is I<NOT> 0-terminated) - this is |
|
|
419 | similar to readlink. |
413 | |
420 | |
414 | =item eio_stat (const char *path, int pri, eio_cb cb, void *data) |
421 | =item eio_stat (const char *path, int pri, eio_cb cb, void *data) |
415 | |
422 | |
416 | =item eio_lstat (const char *path, int pri, eio_cb cb, void *data) |
423 | =item eio_lstat (const char *path, int pri, eio_cb cb, void *data) |
417 | |
424 | |
… | |
… | |
593 | as calling C<fdatasync>. |
600 | as calling C<fdatasync>. |
594 | |
601 | |
595 | Flags can be any combination of C<EIO_SYNC_FILE_RANGE_WAIT_BEFORE>, |
602 | Flags can be any combination of C<EIO_SYNC_FILE_RANGE_WAIT_BEFORE>, |
596 | C<EIO_SYNC_FILE_RANGE_WRITE> and C<EIO_SYNC_FILE_RANGE_WAIT_AFTER>. |
603 | C<EIO_SYNC_FILE_RANGE_WRITE> and C<EIO_SYNC_FILE_RANGE_WAIT_AFTER>. |
597 | |
604 | |
|
|
605 | =item eio_fallocate (int fd, int mode, off_t offset, off_t len, int pri, eio_cb cb, void *data) |
|
|
606 | |
|
|
607 | Calls C<fallocate> (note: I<NOT> C<posix_fallocate>!). If the syscall is |
|
|
608 | missing, then it returns failure and sets C<errno> to C<ENOSYS>. |
|
|
609 | |
|
|
610 | The C<mode> argument can be C<0> (for behaviour similar to |
|
|
611 | C<posix_fallocate>), or C<EIO_FALLOC_FL_KEEP_SIZE>, which keeps the size |
|
|
612 | of the file unchanged (but still preallocates space beyond end of file). |
|
|
613 | |
598 | =back |
614 | =back |
599 | |
615 | |
600 | =head3 LIBEIO-SPECIFIC REQUESTS |
616 | =head3 LIBEIO-SPECIFIC REQUESTS |
601 | |
617 | |
602 | These requests are specific to libeio and do not correspond to any OS call. |
618 | These requests are specific to libeio and do not correspond to any OS call. |
… | |
… | |
677 | |
693 | |
678 | =over 4 |
694 | =over 4 |
679 | |
695 | |
680 | =item eio_req *grp = eio_grp (eio_cb cb, void *data) |
696 | =item eio_req *grp = eio_grp (eio_cb cb, void *data) |
681 | |
697 | |
682 | Creates, submits and returns a group request. |
698 | Creates, submits and returns a group request. Note that it doesn't have a |
|
|
699 | priority, unlike all other requests. |
683 | |
700 | |
684 | =item eio_grp_add (eio_req *grp, eio_req *req) |
701 | =item eio_grp_add (eio_req *grp, eio_req *req) |
685 | |
702 | |
686 | Adds a request to the request group. |
703 | Adds a request to the request group. |
687 | |
704 | |
688 | =item eio_grp_cancel (eio_req *grp) |
705 | =item eio_grp_cancel (eio_req *grp) |
689 | |
706 | |
690 | Cancels all requests I<in> the group, but I<not> the group request |
707 | Cancels all requests I<in> the group, but I<not> the group request |
691 | itself. You can cancel the group request via a normal C<eio_cancel> call. |
708 | itself. You can cancel the group request I<and> all subrequests via a |
|
|
709 | normal C<eio_cancel> call. |
692 | |
710 | |
693 | |
|
|
694 | |
|
|
695 | =back |
711 | =back |
696 | |
712 | |
|
|
713 | =head4 GROUP REQUEST LIFETIME |
|
|
714 | |
|
|
715 | Left alone, a group request will instantly move to the pending state and |
|
|
716 | will be finished at the next call of C<eio_poll>. |
|
|
717 | |
|
|
718 | The usefulness stems from the fact that, if a subrequest is added to a |
|
|
719 | group I<before> a call to C<eio_poll>, via C<eio_grp_add>, then the group |
|
|
720 | will not finish until all the subrequests have finished. |
|
|
721 | |
|
|
722 | So the usage cycle of a group request is like this: after it is created, |
|
|
723 | you normally instantly add a subrequest. If none is added, the group |
|
|
724 | request will finish on it's own. As long as subrequests are added before |
|
|
725 | the group request is finished it will be kept from finishing, that is the |
|
|
726 | callbacks of any subrequests can, in turn, add more requests to the group, |
|
|
727 | and as long as any requests are active, the group request itself will not |
|
|
728 | finish. |
|
|
729 | |
|
|
730 | =head4 CREATING COMPOSITE REQUESTS |
|
|
731 | |
|
|
732 | Imagine you wanted to create an C<eio_load> request that opens a file, |
|
|
733 | reads it and closes it. This means it has to execute at least three eio |
|
|
734 | requests, but for various reasons it might be nice if that request looked |
|
|
735 | like any other eio request. |
|
|
736 | |
|
|
737 | This can be done with groups: |
|
|
738 | |
|
|
739 | =over 4 |
|
|
740 | |
|
|
741 | =item 1) create the request object |
|
|
742 | |
|
|
743 | Create a group that contains all further requests. This is the request you |
|
|
744 | can return as "the load request". |
|
|
745 | |
|
|
746 | =item 2) open the file, maybe |
|
|
747 | |
|
|
748 | Next, open the file with C<eio_open> and add the request to the group |
|
|
749 | request and you are finished setting up the request. |
|
|
750 | |
|
|
751 | If, for some reason, you cannot C<eio_open> (path is a null ptr?) you |
|
|
752 | can set C<< grp->result >> to C<-1> to signal an error and let the group |
|
|
753 | request finish on its own. |
|
|
754 | |
|
|
755 | =item 3) open callback adds more requests |
|
|
756 | |
|
|
757 | In the open callback, if the open was not successful, copy C<< |
|
|
758 | req->errorno >> to C<< grp->errorno >> and set C<< grp->errorno >> to |
|
|
759 | C<-1> to signal an error. |
|
|
760 | |
|
|
761 | Otherwise, malloc some memory or so and issue a read request, adding the |
|
|
762 | read request to the group. |
|
|
763 | |
|
|
764 | =item 4) continue issuing requests till finished |
|
|
765 | |
|
|
766 | In the real callback, check for errors and possibly continue with |
|
|
767 | C<eio_close> or any other eio request in the same way. |
|
|
768 | |
|
|
769 | As soon as no new requests are added the group request will finish. Make |
|
|
770 | sure you I<always> set C<< grp->result >> to some sensible value. |
|
|
771 | |
|
|
772 | =back |
|
|
773 | |
|
|
774 | =head4 REQUEST LIMITING |
697 | |
775 | |
698 | |
776 | |
699 | #TODO |
777 | #TODO |
700 | |
778 | |
701 | /*****************************************************************************/ |
|
|
702 | /* groups */ |
|
|
703 | |
|
|
704 | eio_req *eio_grp (eio_cb cb, void *data); |
|
|
705 | void eio_grp_feed (eio_req *grp, void (*feed)(eio_req *req), int limit); |
|
|
706 | void eio_grp_limit (eio_req *grp, int limit); |
779 | void eio_grp_limit (eio_req *grp, int limit); |
707 | void eio_grp_cancel (eio_req *grp); /* cancels all sub requests but not the group */ |
|
|
708 | |
780 | |
709 | |
781 | |
710 | =back |
782 | =back |
711 | |
783 | |
712 | |
784 | |
… | |
… | |
843 | This symbol governs the stack size for each eio thread. Libeio itself |
915 | This symbol governs the stack size for each eio thread. Libeio itself |
844 | was written to use very little stackspace, but when using C<EIO_CUSTOM> |
916 | was written to use very little stackspace, but when using C<EIO_CUSTOM> |
845 | requests, you might want to increase this. |
917 | requests, you might want to increase this. |
846 | |
918 | |
847 | If this symbol is undefined (the default) then libeio will use its default |
919 | If this symbol is undefined (the default) then libeio will use its default |
848 | stack size (C<sizeof (long) * 4096> currently). If it is defined, but |
920 | stack size (C<sizeof (void *) * 4096> currently). If it is defined, but |
849 | C<0>, then the default operating system stack size will be used. In all |
921 | C<0>, then the default operating system stack size will be used. In all |
850 | other cases, the value must be an expression that evaluates to the desired |
922 | other cases, the value must be an expression that evaluates to the desired |
851 | stack size. |
923 | stack size. |
852 | |
924 | |
853 | =back |
925 | =back |