From: Samuel Just <sjust@redhat.com>
Date: Mon, 10 Jun 2024 21:15:16 +0000 (+0000)
Subject: crimson/.../object_context: remove loading_mutex
X-Git-Tag: v20.0.0~1674^2~5
X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=4ab0578e84f7c78696700dde36219a0c7dd48d0b;p=ceph.git

crimson/.../object_context: remove loading_mutex

Now that we acquire and demote an exclusive lock during loading without
blocking, a seperate loading_mutex shouldn't be necessary.

Signed-off-by: Samuel Just <sjust@redhat.com>
---

diff --git a/src/crimson/osd/object_context.h b/src/crimson/osd/object_context.h
index ae8d1d34a4a..c8349e4fc5c 100644
--- a/src/crimson/osd/object_context.h
+++ b/src/crimson/osd/object_context.h
@@ -74,10 +74,6 @@ public:
   using watch_key_t = std::pair<uint64_t, entity_name_t>;
   std::map<watch_key_t, seastar::shared_ptr<crimson::osd::Watch>> watchers;
 
-  // obc loading is a concurrent phase. In case this obc is being loaded,
-  // make other users of this obc to await for the loading to complete.
-  seastar::shared_mutex loading_mutex;
-
   ObjectContext(hobject_t hoid) : lock(hoid.oid.name),
                                   obs(std::move(hoid)) {}