Re: Large array in KVM

2007-12-17 Thread John Baldwin
On Friday 07 December 2007 06:23:51 am Jeremy Chadwick wrote: > On Fri, Dec 07, 2007 at 10:43:00AM +0100, Gerald Heinig wrote: > > Hi Sonja, > > > > > Hi everyone. > > > > > > I'm working on a kernel module that needs to maintain a large > > structure > > > in memory. As this structure could grow

Re: Large array in KVM

2007-12-08 Thread Robert Watson
On Thu, 6 Dec 2007, Sonja Milicic wrote: I'm working on a kernel module that needs to maintain a large structure in memory. As this structure could grow too big to be stored in memory, it would be good to offload parts of it to the disk. What would be the best way to do this? Could using a me

RE: Large array in KVM

2007-12-07 Thread Gerald Heinig
> On Fri, Dec 07, 2007 at 10:43:00AM +0100, Gerald Heinig wrote: > > Hi Sonja, > > > > > Hi everyone. > > > > > > I'm working on a kernel module that needs to maintain a large > > structure > > > in memory. As this structure could grow too big to be stored in > > memory, > > > it would be good to o

Re: Large array in KVM

2007-12-07 Thread Vlad GALU
On 12/6/07, Sonja Milicic <[EMAIL PROTECTED]> wrote: > Hi everyone. > > I'm working on a kernel module that needs to maintain a large structure > in memory. As this structure could grow too big to be stored in memory, > it would be good to offload parts of it to the disk. What would be the > best w

Re: Large array in KVM

2007-12-07 Thread Daniel O'Connor
On Fri, 7 Dec 2007, Ivan Voras wrote: > Gerald Heinig wrote: > > How about implementing your code as a system call, which is called > > from a process that maps a large file into memory, as you suggested > > above. > > What if the code is a device driver? Then the client process can do some leg wo

Re: Large array in KVM

2007-12-07 Thread Jeremy Chadwick
On Fri, Dec 07, 2007 at 10:43:00AM +0100, Gerald Heinig wrote: > Hi Sonja, > > > Hi everyone. > > > > I'm working on a kernel module that needs to maintain a large > structure > > in memory. As this structure could grow too big to be stored in > memory, > > it would be good to offload parts of it

RE: Large array in KVM

2007-12-07 Thread Gerald Heinig
> Gerald Heinig wrote: > > > How about implementing your code as a system call, which is called from > > a process that maps a large file into memory, as you suggested above. > > What if the code is a device driver? I'm just assuming it isn't a device driver. Sonja (the original poster) just me

Re: Large array in KVM

2007-12-07 Thread Ivan Voras
Gerald Heinig wrote: > How about implementing your code as a system call, which is called from > a process that maps a large file into memory, as you suggested above. What if the code is a device driver? signature.asc Description: OpenPGP digital signature

RE: Large array in KVM

2007-12-07 Thread Gerald Heinig
Hi Sonja, > Hi everyone. > > I'm working on a kernel module that needs to maintain a large structure > in memory. As this structure could grow too big to be stored in memory, > it would be good to offload parts of it to the disk. What would be the > best way to do this? Could using a memory-mappe

Large array in KVM

2007-12-06 Thread Sonja Milicic
Hi everyone. I'm working on a kernel module that needs to maintain a large structure in memory. As this structure could grow too big to be stored in memory, it would be good to offload parts of it to the disk. What would be the best way to do this? Could using a memory-mapped file help? Than

Large array in KVM

2007-12-06 Thread Sonja Milicic
Hi everyone. I'm working on a kernel module that needs to maintain a large structure in memory. As this structure could grow too big to be stored in memory, it would be good to offload parts of it to the disk. What would be the best way to do this? Could using a memory-mapped file help? Than