Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of ignazb@gmail.com designates
 209.85.215.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CA+JKf02AKkgOo2ZrswQSVTWDmfAFgbF0UZvBtQtxZ-Tgj6OQdw@mail.gmail.com>
References: 
 <CA+JKf00k8ph-FT3sRp8fUyZ-_sx9dzMsHzhPALiaMZWncW6QqQ@mail.gmail.com>
	<op.v5oe1lx8ttorjz@lhc>
	<CA+JKf02AKkgOo2ZrswQSVTWDmfAFgbF0UZvBtQtxZ-Tgj6OQdw@mail.gmail.com>
Date: Tue, 29 Nov 2011 10:08:29 +0100
Message-ID: 
 <CAPj=2VB6u_eNZEQHq-R+03ksKMCKmCPbH4_L29YODfp3ndD20w@mail.gmail.com>
Subject: Re: Binary Tree Shared Memory Problem
From: Ignaz Birnstingl <ignazb@gmail.com>
To: modules-dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

> Hi, is there any example mod_slotmem codes that we can understand the
> usage? Or could you give me an usage example?
Sorry, I can't. I haven't used it myself but someone mentioned it in
one of your previous threads.

> And i want to ask a question,
> is it a problem to create
>
> typedef struct node {
> =A0 =A0ELEMENT node_element;
> =A0 =A0struct node *left;
> =A0 =A0struct node *right;
> }NODE;
>
> kind of struct. A struct that has two struct elements.
As I said before the pointers will not work if another process
attaches to the shared memory segment. If only Apache child processes
use the shared memory segment then IMHO the mapping should be the same
(as fork() preserves mappings) and it might be safe to use pointers.
You will need to take a look at your newNode() function: That will
always return the same address; you could keep a counter (inside the
shared memory segment) which tells you where to "allocate" the next
bytes from.

-- Ignaz