All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Riesen <fork0@users.sf.net>
To: Dirk Bull <dirkbull102@hotmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: shmat problem
Date: Mon, 6 Jan 2003 17:22:51 +0100	[thread overview]
Message-ID: <20030106162251.GA15900@steel> (raw)

> Doug, thanks for the reply. I've set SHM_RND in the call and used
> "__attribute__ ((aligned(4096)))" during the the declaration of variable 
> global01_
> (as shown below) such that it is aligned on a page boundary. I'm porting 
> code that was
> written for a Unix system to Linux and the example shown below is how the 
> code is implemented on Unix.

on which exactly?

> The example included executed correctly on:
> mandrake - ? (Can't remember, but it was an old version)
> 
> but fails to work on:
> redhat - 2.2.14-5.0
> debian - 2.2.9
> mandrake - 2.4.19-16mdk
> 
> We are currently working on mandrake - kernel 2.4.19-16mdk.

You have to add SHM_REMAP to shmat flags (see definitions of SHM_ flags).

> 
> 	if ( (shmptr = shmat(shmid, &global01_, SHM_RND)) == (void *) -1)
> 		printf("shmat error: %d %s\n",errno, strerror(errno));
> 	else

add SHM_REMAP.

-alex


             reply	other threads:[~2003-01-06 16:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06 16:22 Alex Riesen [this message]
2003-01-06 16:36 ` shmat problem Doug McNaught
2003-01-06 16:43   ` Alex Riesen
2003-01-06 16:50     ` Doug McNaught
2003-01-06 17:01       ` Alex Riesen
  -- strict thread matches above, loose matches on Subject: below --
2003-01-07  8:14 Dirk Bull
2003-01-07 18:41 ` Alex Riesen
2003-01-06 14:53 Dirk Bull
2003-01-06 15:32 ` Doug McNaught
2003-01-06 15:50   ` Richard B. Johnson
2003-01-06  9:05 Dirk Bull
2003-01-06 14:17 ` Doug McNaught

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=20030106162251.GA15900@steel \
    --to=fork0@users.sf.net \
    --cc=dirkbull102@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.