I'm writing a program which will use Shared Memory (above the
append="mem=XXm" level) for (two-way) communication of large real-time
messages between a module/device-driver and a user-space program.
Because I like to keep things neat and readable (I do know I won't live
forever), a "formal" malloc-like mechanism for Shared Memory would make the
program more self-documenting, certainly more so than with just a bunch of
#defines and the like.
I could fake it since I know this program will be more-or-less the only
thing running -- and certainly the only thing using shared memory --- and
write a one-way pseudo-allocator (which allocates in chunks but deallocates
everything at once when the program terminates). This certainly would
satisfy the code-as-documentation requirement, but it leaves me less than
totally satisfied at its future applicability.
Does anyone have any "simple" malloc/.free code that could be adapted to
this purpose? Or am I making this harder than it already is?
Any suggestions, hints, code, URLs and even constructive flames are welcome,
Norm
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
