luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-06 17:36:14 +01:00
Code Issues Packages Projects Releases Wiki Activity
9f70c964a0
glib/gio/kqueue/kqueue-helper.h

61 lines
2.3 KiB
C
Raw Normal View History

GFileMonitor: Add kqueue(3) support to GIO Written by Dmitry Matveev as part of GSoC 2011: http://netbsd-soc.sourceforge.net/projects/kqueue4gio/ This brings native file monitoring support on systems supporting kqueue(3) (all BSDs) and remove the need to rely on the unmaintained gamin software. The backend adds GKqueueDirectoryMonitor and GKqueueFileMonitor. Some parts rewritten by myself (to prevent needing a configuration file). Helpful inputs from Colin Walters and Simon McVittie. https://bugzilla.gnome.org/show_bug.cgi?id=679793
2012-11-14 12:57:42 +01:00
/*******************************************************************************
Copyright (c) 2011, 2012 Dmitry Matveev <me@dmitrymatveev.co.uk>
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
*******************************************************************************/
#ifndef __KQUEUE_HELPER_H
#define __KQUEUE_HELPER_H
kqueue backend: port to new GLocalFileMonitor API This is the bare minimal effort. This seems not to crash immediately, but it definitely needs some better testing. The backend is not in good shape. It could use some serious work.
2015-01-17 00:51:34 +01:00
#include <gio/glocalfilemonitor.h>
GFileMonitor: Add kqueue(3) support to GIO Written by Dmitry Matveev as part of GSoC 2011: http://netbsd-soc.sourceforge.net/projects/kqueue4gio/ This brings native file monitoring support on systems supporting kqueue(3) (all BSDs) and remove the need to rely on the unmaintained gamin software. The backend adds GKqueueDirectoryMonitor and GKqueueFileMonitor. Some parts rewritten by myself (to prevent needing a configuration file). Helpful inputs from Colin Walters and Simon McVittie. https://bugzilla.gnome.org/show_bug.cgi?id=679793
2012-11-14 12:57:42 +01:00
#include <gio/gfilemonitor.h>
kqueue: Multiple fixes and simplifications - Stop using a custom thread for listening to kqueue(2) events. Instead call kevent(2) in non blocking mode in a monitor callback. Under the hood poll(2) is used to figure out if new events are available. - Do not use a socketpair with a custom protocol requiring 2 supplementary context switches per event to commicate between multiple threads. Calling kevent(2), in non blocking mode, to add/remove events is fine from any context. - Add kqueue(2) events without the EV_ONESHOT flag. This removes a race where some notifications were lost because events had to be re-added for every new notification. - Get rid of the global hash table and its associated lock and races. Use the 'cookie' argument of kevent(2) to pass the associated descriptor when registering an event. - Fix _kh_file_appeared_cb() by properly passing a monitor instead of a source to g_file_monitor_emit_event(). - Properly refcount sources. - Remove a lot of abstraction making it harder to fix the remaining issues. https://bugzilla.gnome.org/show_bug.cgi?id=739424
2018-02-20 17:57:00 +01:00
#include "dep-list.h"
kqueue: Make it possible to pass file monitor tests Previously, kqueue file monitor only add event sources for directories regardless of the type of the file being monitored. Doing so may be possible on inotify, but it is not sufficient on kqueue. Watching a directory on kqueue doesn't report changes made to files under it, and we must watch files themselves to get notified. This problem is fixed by adding a second watch for non-directory file monitors, and the result is that we are now able to receive 'CHANGED' and 'ATTRIBUTE_CHANGED' events for non-directory files. Since having two watches on one file monitor requires many code changes to work properly, this commit also changes the following things: - NOTE_ALL macro is now replaced by note_all inline function. Since the kqueue backend is shared by all BSD operating systems, there are a few difference between these systems. It is easier to do '#ifdef' check in a function than in a macro. - Both g_kqueue_file_monitor_callback and g_kqueue_file_monitor_cancel now holds a lock before accessing kqueue_sub structs. This fixes a crash when these two functions are called from different threads, causing g_kqueue_file_monitor_callback to access freed memory. - 'mask' variable in g_kqueue_file_monitor_callback is now removed. The usage of 'mask' was wrong because of the 'mask > 0' check. 'CHANGED' event has value 0 so the 'mask > 0' check made it impossible to emit 'CHANGED' events. - kqueue-missing scans can now be triggered from the kqueue event callback instead of always waiting for 4 seconds. - Don't remove a file from kqueue on unlink unless its hard link count has dropped to zero. - Don't use 'else if' in the check of 'fflags'. It is possible for a kevent to have multiple flags set. - Don't use g_file_monitor_emit_event directly. Always use g_file_monitor_source_handle_event to report events. Events submitted to g_file_monitor_emit_event are delivered immediately, but events sent to g_file_monitor_source_handle_event are scheduled by GLocalFileMonitor. If we mix the two, the order of events will be wrong and tests will fail. - Report 'CHANGES_DONE_HINT' immediately after 'CREATED' if the file created is not a regular file. This is copied from ih_event_callback.
2018-06-03 13:35:48 +02:00
typedef struct _GKqueueFileMonitor GKqueueFileMonitor;
kqueue: Multiple fixes and simplifications - Stop using a custom thread for listening to kqueue(2) events. Instead call kevent(2) in non blocking mode in a monitor callback. Under the hood poll(2) is used to figure out if new events are available. - Do not use a socketpair with a custom protocol requiring 2 supplementary context switches per event to commicate between multiple threads. Calling kevent(2), in non blocking mode, to add/remove events is fine from any context. - Add kqueue(2) events without the EV_ONESHOT flag. This removes a race where some notifications were lost because events had to be re-added for every new notification. - Get rid of the global hash table and its associated lock and races. Use the 'cookie' argument of kevent(2) to pass the associated descriptor when registering an event. - Fix _kh_file_appeared_cb() by properly passing a monitor instead of a source to g_file_monitor_emit_event(). - Properly refcount sources. - Remove a lot of abstraction making it harder to fix the remaining issues. https://bugzilla.gnome.org/show_bug.cgi?id=739424
2018-02-20 17:57:00 +01:00
/**
* kqueue_sub:
kqueue: Make it possible to pass file monitor tests Previously, kqueue file monitor only add event sources for directories regardless of the type of the file being monitored. Doing so may be possible on inotify, but it is not sufficient on kqueue. Watching a directory on kqueue doesn't report changes made to files under it, and we must watch files themselves to get notified. This problem is fixed by adding a second watch for non-directory file monitors, and the result is that we are now able to receive 'CHANGED' and 'ATTRIBUTE_CHANGED' events for non-directory files. Since having two watches on one file monitor requires many code changes to work properly, this commit also changes the following things: - NOTE_ALL macro is now replaced by note_all inline function. Since the kqueue backend is shared by all BSD operating systems, there are a few difference between these systems. It is easier to do '#ifdef' check in a function than in a macro. - Both g_kqueue_file_monitor_callback and g_kqueue_file_monitor_cancel now holds a lock before accessing kqueue_sub structs. This fixes a crash when these two functions are called from different threads, causing g_kqueue_file_monitor_callback to access freed memory. - 'mask' variable in g_kqueue_file_monitor_callback is now removed. The usage of 'mask' was wrong because of the 'mask > 0' check. 'CHANGED' event has value 0 so the 'mask > 0' check made it impossible to emit 'CHANGED' events. - kqueue-missing scans can now be triggered from the kqueue event callback instead of always waiting for 4 seconds. - Don't remove a file from kqueue on unlink unless its hard link count has dropped to zero. - Don't use 'else if' in the check of 'fflags'. It is possible for a kevent to have multiple flags set. - Don't use g_file_monitor_emit_event directly. Always use g_file_monitor_source_handle_event to report events. Events submitted to g_file_monitor_emit_event are delivered immediately, but events sent to g_file_monitor_source_handle_event are scheduled by GLocalFileMonitor. If we mix the two, the order of events will be wrong and tests will fail. - Report 'CHANGES_DONE_HINT' immediately after 'CREATED' if the file created is not a regular file. This is copied from ih_event_callback.
2018-06-03 13:35:48 +02:00
* @mon: a pointer to the GKqueueFileMonitor which holds this subscription
kqueue: Multiple fixes and simplifications - Stop using a custom thread for listening to kqueue(2) events. Instead call kevent(2) in non blocking mode in a monitor callback. Under the hood poll(2) is used to figure out if new events are available. - Do not use a socketpair with a custom protocol requiring 2 supplementary context switches per event to commicate between multiple threads. Calling kevent(2), in non blocking mode, to add/remove events is fine from any context. - Add kqueue(2) events without the EV_ONESHOT flag. This removes a race where some notifications were lost because events had to be re-added for every new notification. - Get rid of the global hash table and its associated lock and races. Use the 'cookie' argument of kevent(2) to pass the associated descriptor when registering an event. - Fix _kh_file_appeared_cb() by properly passing a monitor instead of a source to g_file_monitor_emit_event(). - Properly refcount sources. - Remove a lot of abstraction making it harder to fix the remaining issues. https://bugzilla.gnome.org/show_bug.cgi?id=739424
2018-02-20 17:57:00 +01:00
* @filename: a name of the file to monitor
* @fd: the associated file descriptor (used by kqueue)
*
kqueue: Make it possible to pass file monitor tests Previously, kqueue file monitor only add event sources for directories regardless of the type of the file being monitored. Doing so may be possible on inotify, but it is not sufficient on kqueue. Watching a directory on kqueue doesn't report changes made to files under it, and we must watch files themselves to get notified. This problem is fixed by adding a second watch for non-directory file monitors, and the result is that we are now able to receive 'CHANGED' and 'ATTRIBUTE_CHANGED' events for non-directory files. Since having two watches on one file monitor requires many code changes to work properly, this commit also changes the following things: - NOTE_ALL macro is now replaced by note_all inline function. Since the kqueue backend is shared by all BSD operating systems, there are a few difference between these systems. It is easier to do '#ifdef' check in a function than in a macro. - Both g_kqueue_file_monitor_callback and g_kqueue_file_monitor_cancel now holds a lock before accessing kqueue_sub structs. This fixes a crash when these two functions are called from different threads, causing g_kqueue_file_monitor_callback to access freed memory. - 'mask' variable in g_kqueue_file_monitor_callback is now removed. The usage of 'mask' was wrong because of the 'mask > 0' check. 'CHANGED' event has value 0 so the 'mask > 0' check made it impossible to emit 'CHANGED' events. - kqueue-missing scans can now be triggered from the kqueue event callback instead of always waiting for 4 seconds. - Don't remove a file from kqueue on unlink unless its hard link count has dropped to zero. - Don't use 'else if' in the check of 'fflags'. It is possible for a kevent to have multiple flags set. - Don't use g_file_monitor_emit_event directly. Always use g_file_monitor_source_handle_event to report events. Events submitted to g_file_monitor_emit_event are delivered immediately, but events sent to g_file_monitor_source_handle_event are scheduled by GLocalFileMonitor. If we mix the two, the order of events will be wrong and tests will fail. - Report 'CHANGES_DONE_HINT' immediately after 'CREATED' if the file created is not a regular file. This is copied from ih_event_callback.
2018-06-03 13:35:48 +02:00
* Represents a subscription on a file or directory. To check whether a
* subscription is active, check the fd field. If fd is not -1, it is an
* active subscription which can emit events from kqueue.
kqueue: Multiple fixes and simplifications - Stop using a custom thread for listening to kqueue(2) events. Instead call kevent(2) in non blocking mode in a monitor callback. Under the hood poll(2) is used to figure out if new events are available. - Do not use a socketpair with a custom protocol requiring 2 supplementary context switches per event to commicate between multiple threads. Calling kevent(2), in non blocking mode, to add/remove events is fine from any context. - Add kqueue(2) events without the EV_ONESHOT flag. This removes a race where some notifications were lost because events had to be re-added for every new notification. - Get rid of the global hash table and its associated lock and races. Use the 'cookie' argument of kevent(2) to pass the associated descriptor when registering an event. - Fix _kh_file_appeared_cb() by properly passing a monitor instead of a source to g_file_monitor_emit_event(). - Properly refcount sources. - Remove a lot of abstraction making it harder to fix the remaining issues. https://bugzilla.gnome.org/show_bug.cgi?id=739424
2018-02-20 17:57:00 +01:00
*/
typedef struct
{
kqueue: Make it possible to pass file monitor tests Previously, kqueue file monitor only add event sources for directories regardless of the type of the file being monitored. Doing so may be possible on inotify, but it is not sufficient on kqueue. Watching a directory on kqueue doesn't report changes made to files under it, and we must watch files themselves to get notified. This problem is fixed by adding a second watch for non-directory file monitors, and the result is that we are now able to receive 'CHANGED' and 'ATTRIBUTE_CHANGED' events for non-directory files. Since having two watches on one file monitor requires many code changes to work properly, this commit also changes the following things: - NOTE_ALL macro is now replaced by note_all inline function. Since the kqueue backend is shared by all BSD operating systems, there are a few difference between these systems. It is easier to do '#ifdef' check in a function than in a macro. - Both g_kqueue_file_monitor_callback and g_kqueue_file_monitor_cancel now holds a lock before accessing kqueue_sub structs. This fixes a crash when these two functions are called from different threads, causing g_kqueue_file_monitor_callback to access freed memory. - 'mask' variable in g_kqueue_file_monitor_callback is now removed. The usage of 'mask' was wrong because of the 'mask > 0' check. 'CHANGED' event has value 0 so the 'mask > 0' check made it impossible to emit 'CHANGED' events. - kqueue-missing scans can now be triggered from the kqueue event callback instead of always waiting for 4 seconds. - Don't remove a file from kqueue on unlink unless its hard link count has dropped to zero. - Don't use 'else if' in the check of 'fflags'. It is possible for a kevent to have multiple flags set. - Don't use g_file_monitor_emit_event directly. Always use g_file_monitor_source_handle_event to report events. Events submitted to g_file_monitor_emit_event are delivered immediately, but events sent to g_file_monitor_source_handle_event are scheduled by GLocalFileMonitor. If we mix the two, the order of events will be wrong and tests will fail. - Report 'CHANGES_DONE_HINT' immediately after 'CREATED' if the file created is not a regular file. This is copied from ih_event_callback.
2018-06-03 13:35:48 +02:00
GKqueueFileMonitor *mon;
kqueue: Multiple fixes and simplifications - Stop using a custom thread for listening to kqueue(2) events. Instead call kevent(2) in non blocking mode in a monitor callback. Under the hood poll(2) is used to figure out if new events are available. - Do not use a socketpair with a custom protocol requiring 2 supplementary context switches per event to commicate between multiple threads. Calling kevent(2), in non blocking mode, to add/remove events is fine from any context. - Add kqueue(2) events without the EV_ONESHOT flag. This removes a race where some notifications were lost because events had to be re-added for every new notification. - Get rid of the global hash table and its associated lock and races. Use the 'cookie' argument of kevent(2) to pass the associated descriptor when registering an event. - Fix _kh_file_appeared_cb() by properly passing a monitor instead of a source to g_file_monitor_emit_event(). - Properly refcount sources. - Remove a lot of abstraction making it harder to fix the remaining issues. https://bugzilla.gnome.org/show_bug.cgi?id=739424
2018-02-20 17:57:00 +01:00
GFileMonitorSource *source;
gchar* filename;
kqueue: Make it possible to pass file monitor tests Previously, kqueue file monitor only add event sources for directories regardless of the type of the file being monitored. Doing so may be possible on inotify, but it is not sufficient on kqueue. Watching a directory on kqueue doesn't report changes made to files under it, and we must watch files themselves to get notified. This problem is fixed by adding a second watch for non-directory file monitors, and the result is that we are now able to receive 'CHANGED' and 'ATTRIBUTE_CHANGED' events for non-directory files. Since having two watches on one file monitor requires many code changes to work properly, this commit also changes the following things: - NOTE_ALL macro is now replaced by note_all inline function. Since the kqueue backend is shared by all BSD operating systems, there are a few difference between these systems. It is easier to do '#ifdef' check in a function than in a macro. - Both g_kqueue_file_monitor_callback and g_kqueue_file_monitor_cancel now holds a lock before accessing kqueue_sub structs. This fixes a crash when these two functions are called from different threads, causing g_kqueue_file_monitor_callback to access freed memory. - 'mask' variable in g_kqueue_file_monitor_callback is now removed. The usage of 'mask' was wrong because of the 'mask > 0' check. 'CHANGED' event has value 0 so the 'mask > 0' check made it impossible to emit 'CHANGED' events. - kqueue-missing scans can now be triggered from the kqueue event callback instead of always waiting for 4 seconds. - Don't remove a file from kqueue on unlink unless its hard link count has dropped to zero. - Don't use 'else if' in the check of 'fflags'. It is possible for a kevent to have multiple flags set. - Don't use g_file_monitor_emit_event directly. Always use g_file_monitor_source_handle_event to report events. Events submitted to g_file_monitor_emit_event are delivered immediately, but events sent to g_file_monitor_source_handle_event are scheduled by GLocalFileMonitor. If we mix the two, the order of events will be wrong and tests will fail. - Report 'CHANGES_DONE_HINT' immediately after 'CREATED' if the file created is not a regular file. This is copied from ih_event_callback.
2018-06-03 13:35:48 +02:00
gchar* basename;
kqueue: Multiple fixes and simplifications - Stop using a custom thread for listening to kqueue(2) events. Instead call kevent(2) in non blocking mode in a monitor callback. Under the hood poll(2) is used to figure out if new events are available. - Do not use a socketpair with a custom protocol requiring 2 supplementary context switches per event to commicate between multiple threads. Calling kevent(2), in non blocking mode, to add/remove events is fine from any context. - Add kqueue(2) events without the EV_ONESHOT flag. This removes a race where some notifications were lost because events had to be re-added for every new notification. - Get rid of the global hash table and its associated lock and races. Use the 'cookie' argument of kevent(2) to pass the associated descriptor when registering an event. - Fix _kh_file_appeared_cb() by properly passing a monitor instead of a source to g_file_monitor_emit_event(). - Properly refcount sources. - Remove a lot of abstraction making it harder to fix the remaining issues. https://bugzilla.gnome.org/show_bug.cgi?id=739424
2018-02-20 17:57:00 +01:00
int fd;
dep_list* deps;
int is_dir;
} kqueue_sub;
gboolean _kqsub_start_watching (kqueue_sub *sub);
kqueue: Make it possible to pass file monitor tests Previously, kqueue file monitor only add event sources for directories regardless of the type of the file being monitored. Doing so may be possible on inotify, but it is not sufficient on kqueue. Watching a directory on kqueue doesn't report changes made to files under it, and we must watch files themselves to get notified. This problem is fixed by adding a second watch for non-directory file monitors, and the result is that we are now able to receive 'CHANGED' and 'ATTRIBUTE_CHANGED' events for non-directory files. Since having two watches on one file monitor requires many code changes to work properly, this commit also changes the following things: - NOTE_ALL macro is now replaced by note_all inline function. Since the kqueue backend is shared by all BSD operating systems, there are a few difference between these systems. It is easier to do '#ifdef' check in a function than in a macro. - Both g_kqueue_file_monitor_callback and g_kqueue_file_monitor_cancel now holds a lock before accessing kqueue_sub structs. This fixes a crash when these two functions are called from different threads, causing g_kqueue_file_monitor_callback to access freed memory. - 'mask' variable in g_kqueue_file_monitor_callback is now removed. The usage of 'mask' was wrong because of the 'mask > 0' check. 'CHANGED' event has value 0 so the 'mask > 0' check made it impossible to emit 'CHANGED' events. - kqueue-missing scans can now be triggered from the kqueue event callback instead of always waiting for 4 seconds. - Don't remove a file from kqueue on unlink unless its hard link count has dropped to zero. - Don't use 'else if' in the check of 'fflags'. It is possible for a kevent to have multiple flags set. - Don't use g_file_monitor_emit_event directly. Always use g_file_monitor_source_handle_event to report events. Events submitted to g_file_monitor_emit_event are delivered immediately, but events sent to g_file_monitor_source_handle_event are scheduled by GLocalFileMonitor. If we mix the two, the order of events will be wrong and tests will fail. - Report 'CHANGES_DONE_HINT' immediately after 'CREATED' if the file created is not a regular file. This is copied from ih_event_callback.
2018-06-03 13:35:48 +02:00
void _kh_dir_diff (kqueue_sub *sub, gboolean handle_deleted);
kqueue: Multiple fixes and simplifications - Stop using a custom thread for listening to kqueue(2) events. Instead call kevent(2) in non blocking mode in a monitor callback. Under the hood poll(2) is used to figure out if new events are available. - Do not use a socketpair with a custom protocol requiring 2 supplementary context switches per event to commicate between multiple threads. Calling kevent(2), in non blocking mode, to add/remove events is fine from any context. - Add kqueue(2) events without the EV_ONESHOT flag. This removes a race where some notifications were lost because events had to be re-added for every new notification. - Get rid of the global hash table and its associated lock and races. Use the 'cookie' argument of kevent(2) to pass the associated descriptor when registering an event. - Fix _kh_file_appeared_cb() by properly passing a monitor instead of a source to g_file_monitor_emit_event(). - Properly refcount sources. - Remove a lot of abstraction making it harder to fix the remaining issues. https://bugzilla.gnome.org/show_bug.cgi?id=739424
2018-02-20 17:57:00 +01:00
void _km_add_missing (kqueue_sub *sub);
kqueue: Make it possible to pass file monitor tests Previously, kqueue file monitor only add event sources for directories regardless of the type of the file being monitored. Doing so may be possible on inotify, but it is not sufficient on kqueue. Watching a directory on kqueue doesn't report changes made to files under it, and we must watch files themselves to get notified. This problem is fixed by adding a second watch for non-directory file monitors, and the result is that we are now able to receive 'CHANGED' and 'ATTRIBUTE_CHANGED' events for non-directory files. Since having two watches on one file monitor requires many code changes to work properly, this commit also changes the following things: - NOTE_ALL macro is now replaced by note_all inline function. Since the kqueue backend is shared by all BSD operating systems, there are a few difference between these systems. It is easier to do '#ifdef' check in a function than in a macro. - Both g_kqueue_file_monitor_callback and g_kqueue_file_monitor_cancel now holds a lock before accessing kqueue_sub structs. This fixes a crash when these two functions are called from different threads, causing g_kqueue_file_monitor_callback to access freed memory. - 'mask' variable in g_kqueue_file_monitor_callback is now removed. The usage of 'mask' was wrong because of the 'mask > 0' check. 'CHANGED' event has value 0 so the 'mask > 0' check made it impossible to emit 'CHANGED' events. - kqueue-missing scans can now be triggered from the kqueue event callback instead of always waiting for 4 seconds. - Don't remove a file from kqueue on unlink unless its hard link count has dropped to zero. - Don't use 'else if' in the check of 'fflags'. It is possible for a kevent to have multiple flags set. - Don't use g_file_monitor_emit_event directly. Always use g_file_monitor_source_handle_event to report events. Events submitted to g_file_monitor_emit_event are delivered immediately, but events sent to g_file_monitor_source_handle_event are scheduled by GLocalFileMonitor. If we mix the two, the order of events will be wrong and tests will fail. - Report 'CHANGES_DONE_HINT' immediately after 'CREATED' if the file created is not a regular file. This is copied from ih_event_callback.
2018-06-03 13:35:48 +02:00
gboolean _km_scan_missing (kqueue_sub *check_this_sub_only);
kqueue: Multiple fixes and simplifications - Stop using a custom thread for listening to kqueue(2) events. Instead call kevent(2) in non blocking mode in a monitor callback. Under the hood poll(2) is used to figure out if new events are available. - Do not use a socketpair with a custom protocol requiring 2 supplementary context switches per event to commicate between multiple threads. Calling kevent(2), in non blocking mode, to add/remove events is fine from any context. - Add kqueue(2) events without the EV_ONESHOT flag. This removes a race where some notifications were lost because events had to be re-added for every new notification. - Get rid of the global hash table and its associated lock and races. Use the 'cookie' argument of kevent(2) to pass the associated descriptor when registering an event. - Fix _kh_file_appeared_cb() by properly passing a monitor instead of a source to g_file_monitor_emit_event(). - Properly refcount sources. - Remove a lot of abstraction making it harder to fix the remaining issues. https://bugzilla.gnome.org/show_bug.cgi?id=739424
2018-02-20 17:57:00 +01:00
void _km_remove (kqueue_sub *sub);
GFileMonitor: Add kqueue(3) support to GIO Written by Dmitry Matveev as part of GSoC 2011: http://netbsd-soc.sourceforge.net/projects/kqueue4gio/ This brings native file monitoring support on systems supporting kqueue(3) (all BSDs) and remove the need to rely on the unmaintained gamin software. The backend adds GKqueueDirectoryMonitor and GKqueueFileMonitor. Some parts rewritten by myself (to prevent needing a configuration file). Helpful inputs from Colin Walters and Simon McVittie. https://bugzilla.gnome.org/show_bug.cgi?id=679793
2012-11-14 12:57:42 +01:00
#endif /* __KQUEUE_HELPER_H */
Reference in New Issue Copy Permalink