rmfreemap(9f) [opensolaris man page]

rmallocmap(9F)						   Kernel Functions for Drivers 					    rmallocmap(9F)

NAME

       rmallocmap, rmallocmap_wait, rmfreemap - allocate and free resource maps

SYNOPSIS

       #include <sys/ddi.h>
       #include <sys/sunddi.h>

       struct map *rmallocmap(size_t mapsize);

       struct map *rmallocmap_wait(size_t mapsize);

       void rmfreemap(struct map *mp);

INTERFACE LEVEL

       Architecture independent level 1 (DDI/DKI).

PARAMETERS

       mapsize	   Number of entries for the map.

       mp	   A pointer to the map structure to be deallocated.

DESCRIPTION

       rmallocmap() dynamically allocates a resource map structure. The argument mapsize defines the total number of entries in the map.  In  par-
       ticular, it is the total number of allocations that can be outstanding at any one time.

       rmallocmap() initializes the map but does not associate it with the actual resource. In	order  to  associate   the  map  with  the  actual
       resource,  a call to rmfree(9F) is used to make the entirety of the actual resource available for allocation, starting from the first index
       into the resource. Typically, the call to rmallocmap() is followed by a call to rmfree(9F), passing the address of the  map  returned  from
       rmallocmap(), the total size of the resource, and the first index into the actual resource.

       The resource map allocated by rmallocmap() can be used to describe an arbitrary resource in whatever allocation units are appropriate, such
       as blocks, pages, or data structures. This resource can then  be  managed  by  the  system  by  subsequent  calls  to   rmalloc(9F),  rmal-
       loc_wait(9F), and rmfree(9F).

       rmallocmap_wait() is similar to	rmallocmap(), with the exception that it will wait for space to become available if necessary.

       rmfreemap() deallocates a resource map structure previously allocated by rmallocmap() or rmallocmap_wait(). The argument mp is a pointer to
       the map structure to be deallocated.

RETURN VALUES

       Upon successful completion, rmallocmap() and  rmallocmap_wait() return a pointer to the newly allocated map structure. Upon failure,  rmal-
       locmap() returns a  NULL pointer.

CONTEXT

       rmallocmap() and rmfreemap() can be called from user, kernel, or interrupt context.

       rmallocmap_wait() can only be called from user or kernel context.

SEE ALSO

       rmalloc(9F), rmalloc_wait(9F), rmfree(9F)

       Writing Device Drivers

SunOS 5.11							    20 Nov 1996 						    rmallocmap(9F)

TM::Synchronizable(3pm) 				User Contributed Perl Documentation				   TM::Synchronizable(3pm)

NAME

       TM::Synchronizable - Topic Maps, trait for synchronizable resources

SYNOPSIS

	  # you write an input/output driver
	  # see for example TM::Synchronizable::MLDBM
	  package My::WhatEver;

	    # provides source_in and/or source_out methods
	    sub source_in  { .... }

	    sub source_out { .... }

	    1;

	  # you construct your map class
	  package MySyncableMap;

	    use TM;
	    use base qw(TM);
	    use Class::Trait qw(TM::ResourceAble TM::Synchronizable My::WhatEver);

	    1;

	  # you then use that
	  my $tm = MySyncableMap (url => 'file:/where/ever');
	  $tm->sync_in;
	  # work with the map, etc...
	  $tm->sync_out;

DESCRIPTION

       This trait implements the abstract synchronization between in-memory topic maps and the resources which are attached to them, i.e. files,
       web pages, etc. whatever can be addressed via a URI.  Consequently, this trait inherits from TM::ResourceAble, although Class::Trait does
       not do this for you (sadly).

       The trait provides the methods "sync_in" and "sync_out" to implement the synchronization. In this process it uses the timestamp of the map
       ("last_mod") and that of the resource "mtime".

       Unfortunately, the granularity of the two are different (at least on current UNIX systems): for the last modification time values from
       Time::HiRes is used. UNIX resources only use an integer.

       Note: This needs a bit of consideration from the user's side.

INTERFACE

   Methods
       sync_in
	   $tm->sync_in

	   This method provides only the main logic, whether a synchronisation from the resource into the in-memory map should occur. If the last
	   modification date of the resource ("mtime") is more recent than that of the map ("last_mod"), then synchronisation from the resource to
	   the in-memory map will be triggered. For this, a method "source_in" has to exist for the map object; that will be invoked.

	   [Since TM 1.53]: Any additional parameters are passed through to the underlying "source_in" method.

       sync_out
	   $tm->sync_out

	   This method provides the logic, whether synchronisation from the in-memory map towards the attached resource should occur or not. If
	   the last modification date of the map ("last_mod") is more recent than that of the resource ("mtime"), then a method "source_out" for
	   the object is triggered.

	   [Since TM 1.53]: Any additional parameters are passed through to the underlying "source_out" method.

SEE ALSO

       TM, TM::ResourceAble

AUTHOR INFORMATION

       Copyright 20(0[6]|10), Robert Barta <drrho@cpan.org>, All rights reserved.

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
       http://www.perl.com/perl/misc/Artistic.html

perl v5.10.1							    2012-06-05						   TM::Synchronizable(3pm)