similar to: mmap shared write support

The patch below adds: - acinclude.m4: A new macro A_FUNC_SMMAP to check that sharing pages through mmap() works. This is taken from Joerg Schilling's star. - configure.in: A_FUNC_SMMAP - ogg123/buffer.c: If we have a working mmap(), use it to create a region of shared memory instead of using System V IPC. Works on BSD. Should also work on SVR4 and offspring (Solaris), and Linux.

http://bugzilla.mindrot.org/show_bug.cgi?id=303 Summary: conftest fails to determine mmap anon shared Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org

Hi, We are porting some applications from CentOS 4 to CentOS 5, the applications use mmap, and we found out that they sometimes crash in CentOS 5. We found out that this is due to the fact that CentOS 5 does randomization of the address space when loading binaries, libraries, and when using mmap, so that is what's causing our problem. The thing is, I'm trying to google for it, but I did

On Tue, Jul 18, 2017 at 10:48:45AM +0200, Jan Wrona wrote: > Hi, > > I need to use rrdtool on top of a Gluster FUSE mount, rrdtool uses > memory-mapped file IO extensively (I know I can recompile rrdtool with > mmap() disabled, but that is just a workaround). I have three FUSE mount > points on three different servers, on one of them the command "rrdtool > create

I'm trying to use dovecot-deliver with sieve plugin, delivering to Maildirs. Everything seems working O.K., but I'm getting the following lines in /var/log/maillog: --- Mar 29 00:06:00 alt64 dovecot: imap-login: Login: user=<seriv>, method=PLAIN, rip=66.80.117.2, lip=192.168.10.8, TLS Mar 29 00:06:00 alt64 dovecot: IMAP(seriv): mmap() failed with index file

Good morning, We are trying to figure out how to properly provide adresss hints to mmap on 32-bit Centos 5.5. Does any documentation exist about to how to provide address hints to mmap on 32-bit Centos 5.5? If so, where can we find this documentation. In order to understand mmap better, we decided to try to find the Centos 5.5 source code for mmap.c. We already installed the kernel source

On 18.7.2017 12:17, Niels de Vos wrote: > On Tue, Jul 18, 2017 at 10:48:45AM +0200, Jan Wrona wrote: >> Hi, >> >> I need to use rrdtool on top of a Gluster FUSE mount, rrdtool uses >> memory-mapped file IO extensively (I know I can recompile rrdtool with >> mmap() disabled, but that is just a workaround). I have three FUSE mount >> points on three different

http://bugzilla.mindrot.org/show_bug.cgi?id=322 Summary: Anon shared MMAP test fails wrongly under FreeBSD Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: FreeBSD Status: NEW Severity: minor Priority: P3 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org

I thought I would forward this to see if anyone has any suggestions (other than, "You shouldn''t use this code in conjunction with fork"). Thanks, Dan ----- Forwarded Message ---- From: "Park, Chong SuhX" <chong.suhx.park at intel.com> To: Daniel Berger <djberg96 at yahoo.com> Sent: Monday, October 16, 2006 3:59:55 PM Subject: mmap 0.2.0 writing value

Hi all, I have committed win32-mmap package. It is similar to mmap or shared memory of unix Basically, it can be used for variable sharing like this In server side ================================== m = Mmap.new a = 1 m.setvar("a",a) =================================== In client side ================================== m = Mmap.new(''reuse''=>true) a =

Switch gem shmem helper to the new mmap() workflow, from &gem_driver.fops.mmap to &drm_gem_object_funcs.mmap. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- include/drm/drm_gem_shmem_helper.h | 6 ++---- drivers/gpu/drm/drm_gem_shmem_helper.c | 26 ++++++++----------------- drivers/gpu/drm/panfrost/panfrost_gem.c | 2 +- drivers/gpu/drm/v3d/v3d_bo.c | 2

From: Heiko Carstens <heiko.carstens@de.ibm.com> Fix mmap compilation (missing errno.h include) and use correct minimum error number for compare. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> --- Does not compile in akpm's latest -mm tree. usr/klibc/arch/s390/mmap.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git

On Thu, Oct 29, 2015 at 09:19:03AM -0500, Jason Pepas wrote: > Hi, > > I'm new to nbdkit and am trying to run a simple "single file block > device using mmap" setup, using this python script: > > import mmap > > def config(key, value): > print ("ignored parameter %s=%s" % (key, value)) > > def open(readonly): > print

Switch gem shmem helper to the new mmap() workflow, from &gem_driver.fops.mmap to &drm_gem_object_funcs.mmap. v2: Fix vm_flags and vm_page_prot handling. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- include/drm/drm_gem_shmem_helper.h | 6 ++---- drivers/gpu/drm/drm_gem_shmem_helper.c | 28 +++++++++---------------- drivers/gpu/drm/panfrost/panfrost_gem.c | 2 +-

Switch gem shmem helper to the new mmap() workflow, from &gem_driver.fops.mmap to &drm_gem_object_funcs.mmap. v2: Fix vm_flags and vm_page_prot handling. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- include/drm/drm_gem_shmem_helper.h | 6 ++---- drivers/gpu/drm/drm_gem_shmem_helper.c | 28 +++++++++---------------- drivers/gpu/drm/panfrost/panfrost_gem.c | 2 +-

Switch gem shmem helper to the new mmap() workflow, from &gem_driver.fops.mmap to &drm_gem_object_funcs.mmap. v2: Fix vm_flags and vm_page_prot handling. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> Reviewed-by: Steven Price <steven.price at arm.com> --- include/drm/drm_gem_shmem_helper.h | 6 ++---- drivers/gpu/drm/drm_gem_shmem_helper.c | 28

Am 07.02.19 um 09:59 schrieb Thomas Zimmermann: > Almost all TTM-based drivers use the same values for the mmap-able > range of BO addresses. Each driver therefore duplicates the > DRM_FILE_PAGE_OFFSET constant. OTOH, the mmap range's size is not > configurable by drivers. > > This patch set replaces driver-specific configuration with a single > setup. All code is located

Hi, On 2/7/19 9:59 AM, Thomas Zimmermann wrote: > Almost all TTM-based drivers use the same values for the mmap-able > range of BO addresses. Each driver therefore duplicates the > DRM_FILE_PAGE_OFFSET constant. OTOH, the mmap range's size is not > configurable by drivers. > > This patch set replaces driver-specific configuration with a single > setup. All code is

Hi, On 07-02-19 09:59, Thomas Zimmermann wrote: > Almost all TTM-based drivers use the same values for the mmap-able > range of BO addresses. Each driver therefore duplicates the > DRM_FILE_PAGE_OFFSET constant. OTOH, the mmap range's size is not > configurable by drivers. > > This patch set replaces driver-specific configuration with a single > setup. All code is

Hi, On 11-03-19 17:51, Christian K?nig wrote: > Am 11.03.19 um 17:39 schrieb Hans de Goede: >> Hi, >> >> On 07-02-19 09:59, Thomas Zimmermann wrote: >>> Almost all TTM-based drivers use the same values for the mmap-able >>> range of BO addresses. Each driver therefore duplicates the >>> DRM_FILE_PAGE_OFFSET constant. OTOH, the mmap range's size