diff options
author | Alexander Aring <aahringo@redhat.com> | 2024-08-02 13:26:43 -0400 |
---|---|---|
committer | David Teigland <teigland@redhat.com> | 2024-08-08 15:15:08 -0500 |
commit | 94e180d6255f5a765bb723e6e8b67f1438ce574b (patch) | |
tree | 3735a7c0ad058819b8de99d1a479c77f137d050f /lib/test_bpf.c | |
parent | 8a4cf500f1dded74ababd8d33db35631e540e124 (diff) |
dlm: async freeing of lockspace resources
This patch handles freeing of lockspace resources asynchronously besides
the release_lockspace() context. The release_lockspace() context is
sometimes called in a time critical context, e.g. umount syscall. Most
every user space init system will timeout if it takes too long. To
reduce the potential waiting time we deregister in release_lockspace()
the lockspace from the DLM subsystem and do the actual releasing of
lockspace resource in a worker of a workqueue following recommendation
of:
https://lore.kernel.org/all/49925af7-78a8-a3dd-bce6-cfc02e1a9236@I-love.SAKURA.ne.jp/T/#u
as flushing of system workqueues are not allowed. The most time to
release the DLM resources are spent to release the data structures
"ls->ls_lkbxa" and "ls->ls_rsbtbl" as they iterate over each entries and
those data structures can contain millions of entries. This patch handles
for now only freeing of those data structures as those operations are
the most reason why release_lockspace() blocking of being returned.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
Diffstat (limited to 'lib/test_bpf.c')
0 files changed, 0 insertions, 0 deletions