From: Alexey Lyashkov via lustre-devel <lustre-devel@lists.lustre.org>
To: "Degremont, Aurelien" <degremoa@amazon.com>
Cc: Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [lustre-devel] LDLM behaviour question
Date: Fri, 12 Mar 2021 07:36:05 +0300 [thread overview]
Message-ID: <5BFA79A7-96F0-4C71-8266-5460DFD7A0F6@cloudlinux.com> (raw)
In-Reply-To: <B489BBDF-36DA-4B79-BCB3-19FBBEEF75E2@amazon.com>
[-- Attachment #1.1: Type: text/plain, Size: 1113 bytes --]
Aurélien,
> 8 марта 2021 г., в 17:09, Degremont, Aurelien via lustre-devel <lustre-devel@lists.lustre.org> написал(а):
>
> Hi all,
>
> I was not able to find a document giving this level of detail of LDLM behavior.
I think this aged book will good start. https://wiki.lustre.org/images/d/da/Understanding_Lustre_Filesystem_Internals.pdf <https://wiki.lustre.org/images/d/da/Understanding_Lustre_Filesystem_Internals.pdf>
> I have a basic question regarding compatibility between IBITS lock for the same fid.
>
> Is it possible for the same MDT to lock the same FID, with 2 IBITS lock, with different bits? (ie: UPDATE vs LAYOUT)
> What's the behavior is not working?
>
Yes, this is possible. Same story as LOOKUP, OPEN, DOM …
> Second question: what happen when you call multiple times mdt_object_lock() for the same fid/same bits on the same MDT?
>
> Thanks
>
> Aurélien
>
> _______________________________________________
> lustre-devel mailing list
> lustre-devel@lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
[-- Attachment #1.2: Type: text/html, Size: 2270 bytes --]
[-- Attachment #2: Type: text/plain, Size: 165 bytes --]
_______________________________________________
lustre-devel mailing list
lustre-devel@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
prev parent reply other threads:[~2021-03-12 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 14:09 [lustre-devel] LDLM behaviour question Degremont, Aurelien via lustre-devel
2021-03-12 4:36 ` Alexey Lyashkov via lustre-devel [this message]
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=5BFA79A7-96F0-4C71-8266-5460DFD7A0F6@cloudlinux.com \
--to=lustre-devel@lists.lustre.org \
--cc=degremoa@amazon.com \
--cc=umka@cloudlinux.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).