From: Louis Rilling <Louis.Rilling@kerlabs.com>
To: Martin Uecker <muecker@gwdg.de>
Cc: Steven Whitehouse <swhiteho@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: distributed shared memory / mmap
Date: Wed, 20 Aug 2008 17:04:08 +0200 [thread overview]
Message-ID: <20080820150408.GE581@hawkmoon.kerlabs.com> (raw)
In-Reply-To: <1219243404.20622.156.camel@quoit>
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
On Wed, Aug 20, 2008 at 03:43:24PM +0100, Steven Whitehouse wrote:
> Hi,
>
> On Wed, 2008-08-20 at 15:18 +0200, Martin Uecker wrote:
> >
> > Hi!
> >
> > Is there any easy way to get shared memory between to
> > processes on different machines? It seems possible using mmap
> > on a file system like GFS on top of a distributed block device.
> >
> >
> > Sincerly,
> > Martin Uecker
> >
> Yes, you can do it using GFS/GFS2 and it should work. On the other hand,
> don't do it. Its probably not what you want and unlikely to give you
> good performance since the locking is "per inode" and thus you'll
> generate a lot of cache flushing if there is any appreciable amount of
> writing to the shared region. If you have a read mostly (or only)
> workload, then it will work much better.
Alternatively, you can use kernel-level DSM like provided by Kerrighed.
Kerrighed provides cluster-wide SYSV shm segments, which sharing is handled
at the page level -> far better than the inode level.
You may find this solution not-so-easy though...
Regards,
Louis
--
Dr Louis Rilling Kerlabs
Skype: louis.rilling Batiment Germanium
Phone: (+33|0) 6 80 89 08 23 80 avenue des Buttes de Coesmes
http://www.kerlabs.com/ 35700 Rennes
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-08-20 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 13:18 Martin Uecker
2008-08-20 14:43 ` Steven Whitehouse
2008-08-20 15:04 ` Louis Rilling [this message]
2008-08-20 15:27 ` Mark Hounschell
2008-08-20 17:00 ` linux-os (Dick Johnson)
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=20080820150408.GE581@hawkmoon.kerlabs.com \
--to=louis.rilling@kerlabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=muecker@gwdg.de \
--cc=swhiteho@redhat.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
Powered by JetHome