From: Jeff Dike <jdike@addtoit.com>
To: Allan Graves <allan.graves@oracle.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] os_lock_file removal
Date: Fri, 24 Jun 2005 17:15:33 -0400 [thread overview]
Message-ID: <20050624211533.GA10972@ccure.user-mode-linux.org> (raw)
In-Reply-To: <42BC5CD9.2080005@oracle.com>
On Fri, Jun 24, 2005 at 03:19:53PM -0400, Allan Graves wrote:
> 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.
Feel free to remove it if you personally guarantee that you will not run
two UMLs on the same host file without using a clusterfs.
It's purely a safety measure - if you're doing development using scratch
filesystems, it's not really benefitting you.
Jeff
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2005-06-24 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 19:19 [uml-devel] os_lock_file removal Allan Graves
2005-06-24 21:15 ` Jeff Dike [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=20050624211533.GA10972@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox