linux-kernel - Re: distributed shared memory / mmap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 20 Aug 2008 15:43:24 +0100
From:	Steven Whitehouse <swhiteho@...hat.com>
To:	Martin Uecker <muecker@...g.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: distributed shared memory / mmap

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.

There are often better solutions though, depending on the application in
question,

Steve.



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/