At 6:16 PM -0700 8/14/00, Bill Studenmund wrote:
>On Sun, 13 Aug 2000, gabriel rosenkoetter wrote:
> case, this means changing the UVM structure such that the RAM of
> > another computer in a cluster can be used as backing store in place
> > of disk. I need access to considerably more than printf(), memcpy(),
> > and extraneous other functions (specifically, I want to rewrite
> > uvm_page(), pgo_get(), and related functions from sys/uvm).
>
>I'm not sure, but I think what you want to do is add a new kind of swap
>ability. I'm not sure how easy it is to add one, but your project
>certainly argues for the ability. I'm not sufficiently familiar with the
>uvm code to say.
>
>Also, I think that it's hard to change existing kernel routines. The
>linking process, as I understand it, will modify unresolved symbols in
>your lkm to point to the in-kernel ones. But it will not modify existing
>kernel references to other kernel functions (like existing calls to
>uvm_page()) to point out to your lkm code.

There is already support for swapping to a vnode filesystem.  Sounds 
like what you should be doing is defining the vnode calls to swap 
page data, not modifying UVM itself.


Signature held pending an ISO 9000 compliant
signature design and approval process.
h.b.hotz@jpl.nasa.gov, or hbhotz@oxy.edu