summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorJean-Sébastien Pédron <jean-sebastien@rabbitmq.com>2017-05-09 11:32:20 +0200
committerJean-Sébastien Pédron <jean-sebastien@rabbitmq.com>2017-05-19 16:34:31 +0200
commit58d7abdd8b1634f6c839ac4cc3846f6e59a365f2 (patch)
treefdc27c42eb9f1291be78e5962bab3e6f0817b284 /include
parentced8290812301cb2101b429d0cf1a6d7916daba2 (diff)
downloadrabbitmq-server-git-58d7abdd8b1634f6c839ac4cc3846f6e59a365f2.tar.gz
Move rabbit_memory_monitor:memory_use/1 to vm_memory_monitor
The function is renamed to get_memory_use/1 in the process, to match other functions in the vm_memory_monitor module. The file_handle_cache uses that function. By moving it to vm_memory_monitor, we remove a dependency of file_handle_cache on a rabbit_* module. This will allow us to move both file_handle_cache and vm_memory_monitor to rabbitmq-common and help remove a dependency in the Erlang client on the broker because the former calls file_handle_cache:obtain/0. To sum up the situation before this commit with a graph: amqp_network_connection --[depends on]--> file_handle_cache (amqp_client) (rabbit) file_handle_cache --[depends on]--> rabbit_memory_monitor (rabbit) (rabbit) And the situation we want to reach after the move: amqp_network_connection --[depends on]--> file_handle_cache (amqp_client) (rabbit_common) file_handle_cache --[depends on]--> vm_memory_monitor (rabbit_common) (rabbit_common) rabbit_memory_monitor --[depends on]--> vm_memory_monitor (rabbit) (rabbit_common) [#118490793]
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions