From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Avoid mandatory locks? Really? According to linux/Documentation/filesystems/mandatory-locking.txt
Date: Wed, 30 Mar 2011 22:11:04 +0700 [thread overview]
Message-ID: <AANLkTikDkJYd3V6T1xsfsGynVjoinWx3pUqPb2oska0t@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik4PXTe_vaXYoWqX4pFHJJDrRuPfr+M1ONr7xuE@mail.gmail.com>
On Wed, Mar 30, 2011 at 22:08, Kevin O'Gorman <kogorman@gmail.com> wrote:
> That may be an overstatement. ?Most of the complaints are about DoS attacks
> and/or
> distributed systems. ?That's pretty awful, and means the locking is not
> scaleable, but
alright...maybe that's why, e.g in distributed fs such as GFS, we need
(gfs) lockd or something like that...ok, now I could guess, that's due
to some of POSIX lock weaknesses.. CMIIW
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2011-03-30 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 2:14 Avoid mandatory locks? Really? According to linux/Documentation/filesystems/mandatory-locking.txt Kevin O'Gorman
2011-03-30 5:54 ` Michael Blizek
2011-03-30 14:47 ` Mulyadi Santosa
[not found] ` <AANLkTik4PXTe_vaXYoWqX4pFHJJDrRuPfr+M1ONr7xuE@mail.gmail.com>
2011-03-30 15:11 ` Mulyadi Santosa [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=AANLkTikDkJYd3V6T1xsfsGynVjoinWx3pUqPb2oska0t@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).