From: Byungchul Park <byungchul@sk.com>
To: aahringo@redhat.com
Cc: kernel_team@skhynix.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] DEPT(DEPendency Tracker) with DLM(Distributed Lock Manager)
Date: Thu, 22 May 2025 14:28:06 +0900 [thread overview]
Message-ID: <20250522052806.GB42746@system.software.com> (raw)
In-Reply-To: <20250522052453.GA42746@system.software.com>
On Thu, May 22, 2025 at 02:24:53PM +0900, Byungchul Park wrote:
> Hi Alexander,
>
> We briefly talked about dept with DLM in an external channel. However,
> it'd be great to discuss what to aim and how to make it in more detail,
> in this mailing list.
>
> It's worth noting that dept doesn't track dependencies beyond different
> contexts to avoid adding false dependencies by any chance, which means
> though dept checks the dependency sanity *globally*, when it comes to
> creating dependencies, it happens only within e.g. each single system
> call context, each single irq context, each worker context, and so on,
> with its unique context id assigned to each independent context.
>
> In order for dept to work on DLM, we need a way to assign a unique
> context id to each interesting context in DLM's point of view, and let
> dept know the id. Once making it done, I think dept can work on DLM
> perfectly.
Plus, we need a way to share the global dependency graph used by dept
between nodes too.
Byungchul
>
> Thoughts or any concern?
>
> Byungchul
next prev parent reply other threads:[~2025-05-22 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 5:24 [RFC] DEPT(DEPendency Tracker) with DLM(Distributed Lock Manager) Byungchul Park
2025-05-22 5:28 ` Byungchul Park [this message]
2025-05-26 0:13 ` Alexander Aring
2025-05-28 12:00 ` Alexander Aring
2025-05-29 7:22 ` Byungchul Park
2025-05-26 0:11 ` Alexander Aring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250522052806.GB42746@system.software.com \
--to=byungchul@sk.com \
--cc=aahringo@redhat.com \
--cc=kernel_team@skhynix.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox