- remove the note about the PGK_MEM_POOL_SIZE, this is already fixed

  in the trunk


git-svn-id: https://openser.svn.sourceforge.net/svnroot/openser/trunk@5033 689a6050-402a-0410-94f2-e92a70836424

modules/carrierroute/README

@@ -187,11 +187,6 @@ Chapter 1. Admin Guide
    much tested at the moment. In load balancing scenarios the
    usage of the config file mode is recommended, to avoid the
    additional complexity that the database driven routing creates.
-   Please note: although the routing tree is stored in shared
-   memory, for the initial loading from the database on startup
-   private memory is allocated. Thus you'll probably need to
-   increase the private memory pool size. For 40.000 routing rules
-   a "PKG_MEM_POOL_SIZE" of 10 MB is sufficient.
 
    Routing tables can be reloaded and edited (in config file mode)
    with the MI interface, the config file is updated according the

modules/carrierroute/doc/carrierroute_admin.xml

@@ -25,10 +25,7 @@
 		more than several hundred thousand routing table entries. It should be able to handle
 		more, but this is not that much tested at the moment. In load balancing scenarios the
 		usage of the config file mode is recommended, to avoid the additional complexity that
-		the database driven routing creates. Please note: although the routing tree is stored
-		in shared memory, for the initial loading from the database on startup private memory
-		is allocated. Thus you'll probably need to increase the private memory pool size. For
-		40.000 routing rules a <quote>PKG_MEM_POOL_SIZE</quote> of 10 MB is sufficient.
+		the database driven routing creates.
 	</para>
 	<para>
 		Routing tables can be reloaded and edited (in config file mode) with the MI