From: Allan Graves <allan.graves@oracle.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] os_lock_file removal
Date: Fri, 24 Jun 2005 15:19:53 -0400 [thread overview]
Message-ID: <42BC5CD9.2080005@oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
Hi guys. I'm working on developing a cluster file system and I'd like
to simulate concurrent shared storage access using uml and disk files.
I traced down the file locking, and it seems that (assuming I have a
cluster file system that keeps things up to date in the metadata of the
filesystem) if I remove this function I should be able to have more than
1 instance accessing storage at the same time. I realize this is a bit
dangerous, since it involves *all* block devices, but I don't see a
much better way. COW is not what I'm looking for, and that seems to be
the standard answer. Can anyone provide positive or negative feedback
on this approach? Possibly a better approach?
Thanks,
Allan Graves
[-- Attachment #2: allan.graves.vcf --]
[-- Type: text/x-vcard, Size: 147 bytes --]
begin:vcard
fn:Allan Graves
n:Graves;Allan
email;internet:allan.graves@oracle.com
tel;work:603-8973276
x-mozilla-html:FALSE
version:2.1
end:vcard
next reply other threads:[~2005-06-24 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 19:19 Allan Graves [this message]
2005-06-24 21:15 ` [uml-devel] os_lock_file removal Jeff Dike
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=42BC5CD9.2080005@oracle.com \
--to=allan.graves@oracle.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.