Can you tell us more about this whole thing? What's the rough difference
   to our current scheme, does one use it in kernel config files, ... ?


the code commit log had more info:


   add new version of non contiguous memory code, written by chuck cranor,
   called "MACHINE_NEW_NONCONGIG".  this is required for UVM, the new VM
   system (also written by chuck) that is coming soon.  adds new functions:
	vm_page_physload() -- tell the VM system about an area of memory.
	vm_physseg_find() -- returns index in vm_physmem array that this
		address is in.
   and several new versions of old functions/macros defined in vm_page.h.


in general, a user will not need to worry about this.  when ready, a
port master will switch their port to use this by default.  when all
ports are converted, the old code (contig, and old non-contig cases)
will be removed.


.mrg.