OK, if I understand you correctly it would _technically_ work, but I
wouldn't want to use it. Here's why:

1) If I'm doing memory allocations I might (probably am?) interested in
performance, and while data queues aren't slow they're a hell of a lot
slower than memory IOs.

2) If I'm using teraspace instead of "normal" space then I'm probably also
interested in allocations > 16Meg. Given that there is a 16Meg limit on a
dataq I'd hit a problem there too.

-Walden

------------
Walden H Leverich III
President
Tech Software
(516)627-3800 x11
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com



-----Original Message-----
From: David & Eileen Keck [mailto:bstars@optonline.net]
Sent: Wednesday, December 26, 2001 13:32
To: midrange-l@midrange.com
Subject: Re: Teraspace memory allocation


Walden,
    I understand that teraspace can not be directly shared across multiple
jobs, but that's really not much of an impediment to sharing teraspace.  You
just do it indirectly.  If you create a job which allocates an instance of
teraspace, and this job runs in batch as a daemon, it can provide shared
access to common teraspace across all other jobs in your system.  Other jobs
can communicate with the Teraspace Server via two data queues.  One to send
requests to the server, the other to send result sets back to the client.  A
request to the server could contain a function code, a handle, and data. The
result would be just handle and data.  The handle/address cross reference
could be stored in an array or based data structure in the server program,
and the cookie/handle would be the array pointer or based data structure
offset, depending on which way you went.  Why wouldn't such a mechanism work
?  -Dave K.

----- Original Message -----
From: "Walden H. Leverich" <WaldenL@TechSoftInc.com>
To: <midrange-l@midrange.com>
Sent: Wednesday, December 26, 2001 12:00 PM
Subject: RE: Teraspace memory allocation


> Dave,
>
> Actually, the manual says teraspace allocations are valid only in the
> job that does the allocation, if you want to share the allocations
> then you
need
> to deal with the share memory apis. Now, if you are referencing
> teraspace with a space pointer I'm not sure how that would play out,
> on one hand teraspace is only valid in the job that allocates it, on
> the other hand a space pointer is a space pointer from any job.
>
> -Walden
>
> ------------
> Walden H Leverich III
> President
> Tech Software
> (516)627-3800 x11
> WaldenL@TechSoftInc.com
> http://www.TechSoftInc.com
>
>
>
> -----Original Message-----
> From: David & Eileen Keck [mailto:bstars@optonline.net]
> Sent: Monday, December 24, 2001 11:11
> To: midrange-l@midrange.com
> Subject: Re: Teraspace memory allocation
>
>
> I beg to differ.  As I suggested in a previous post on this topic, a
> Teraspace Server process could be set up as a daemon.  From a design
> point of view, mutiple jobs can certainly share the same teraspace by
referencing
> the same handle / cookie. Dave K.
>
> ----- Original Message -----
> From: "Simon Coulter" <shc@flybynight.com.au>
> To: <midrange-l@midrange.com>
> Sent: Saturday, December 22, 2001 10:08 PM
> Subject: Re: Teraspace memory allocation
>
> ----snip ----------
> >  TS exists only
> > for the duration of a job/process thus a handle cannot be stored
> externally
> > to the process and reused in a different process.
> ----snip-----------
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com To subscribe,
unsubscribe,
> or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives at
> http://archive.midrange.com/midrange-l.
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives at
> http://archive.midrange.com/midrange-l.
>

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.