On Fri, 20 Apr 2001, Stephen C. Tweedie wrote:
> On Fri, Apr 20, 2001 at 03:49:30PM +0100, Alan Cox wrote:
>
> > There is a proposal (several it seems) to make 2.5 replace the conventional
> > unix swap with a filesystem of backing store for anonymous objects. That will
> > mean each object has
On Fri, 20 Apr 2001, Stephen C. Tweedie wrote:
On Fri, Apr 20, 2001 at 03:49:30PM +0100, Alan Cox wrote:
There is a proposal (several it seems) to make 2.5 replace the conventional
unix swap with a filesystem of backing store for anonymous objects. That will
mean each object has its own
Hi,
On Fri, Apr 20, 2001 at 03:49:30PM +0100, Alan Cox wrote:
> There is a proposal (several it seems) to make 2.5 replace the conventional
> unix swap with a filesystem of backing store for anonymous objects. That will
> mean each object has its own vm area and inode and thus we can start
> compared to the complexity that gets added to the kernel. We can keep the
> kernel simpler(and faster) without having parts of drivers pageable. But one
> more issue is having the page tables pageable...
At the moment we can almost go a stage further - when we are short of memory
we can
> > VMS does this. It at least used to have a great tendency to crash
> > itself, because it swapped out something that was called from a driver
> > that was called by the swapper -- resulting in deadlock. You need
> > iron discipline for this to work right in all circumstances.
>
> Actually,
On Tue, 17 Apr 2001, Oliver Neukum did have cause to say:
> > load/init/etc. Hardware setup tends to only happen once..)
>
> No they can't. Modules can't be finegrained enough to do this without wasting
> more memory due to fragmentation than you'd gain.
Actually, don't they do this
Hi,
On Tue, Apr 17, 2001 at 12:21:17PM -0700, H. Peter Anvin wrote:
> > Certain parts of drivers could get the __pageable prefix or so
> > (like the __init parts of drivers which get removed) for letting
> > the paging-code know that it can be discared if memory-pressure
> > demands it.
>
>
Hi,
On Tue, Apr 17, 2001 at 12:21:17PM -0700, H. Peter Anvin wrote:
Certain parts of drivers could get the __pageable prefix or so
(like the __init parts of drivers which get removed) for letting
the paging-code know that it can be discared if memory-pressure
demands it.
VMS does
On Tue, 17 Apr 2001, Oliver Neukum did have cause to say:
load/init/etc. Hardware setup tends to only happen once..)
No they can't. Modules can't be finegrained enough to do this without wasting
more memory due to fragmentation than you'd gain.
Actually, don't they do this -already-? I
VMS does this. It at least used to have a great tendency to crash
itself, because it swapped out something that was called from a driver
that was called by the swapper -- resulting in deadlock. You need
iron discipline for this to work right in all circumstances.
Actually, VMS doesn't
compared to the complexity that gets added to the kernel. We can keep the
kernel simpler(and faster) without having parts of drivers pageable. But one
more issue is having the page tables pageable...
At the moment we can almost go a stage further - when we are short of memory
we can
Hi,
On Fri, Apr 20, 2001 at 03:49:30PM +0100, Alan Cox wrote:
There is a proposal (several it seems) to make 2.5 replace the conventional
unix swap with a filesystem of backing store for anonymous objects. That will
mean each object has its own vm area and inode and thus we can start blowing
H. Peter Anvin writes:
> By author:"Heusden, Folkert van" <[EMAIL PROTECTED]>
>> Would anyone be intrested (besides me) in a kernel which can page
...
>> Certain parts of drivers could get the __pageable prefix or so
> VMS does this. It at least used to have a great tendency to crash
>
Followup to: <[EMAIL PROTECTED]>
By author:"Heusden, Folkert van" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Would anyone be intrested (besides me) in a kernel which can page
> out certain parts of itself? The kernel should be in some kind of
> vmlinux-ish (as in: uncompressed)
On Tue, 17 Apr 2001, Heusden, Folkert van did have cause to say:
> I would think is usable (for example) for my 8MB ram laptop.
> Anyone any thoughts on this?
I'm not a kernel hacker, but I've got some thoughts on this:
1> Modules (with the autoloader) can do that for anything not necessary to
Would anyone be intrested (besides me) in a kernel which can page
out certain parts of itself? The kernel should be in some kind of
vmlinux-ish (as in: uncompressed) format on disk for on-demand
re-loading of pages which are discarded.
Certain parts of drivers could get the __pageable prefix or
Would anyone be intrested (besides me) in a kernel which can page
out certain parts of itself? The kernel should be in some kind of
vmlinux-ish (as in: uncompressed) format on disk for on-demand
re-loading of pages which are discarded.
Certain parts of drivers could get the __pageable prefix or
On Tue, 17 Apr 2001, Heusden, Folkert van did have cause to say:
I would think is usable (for example) for my 8MB ram laptop.
Anyone any thoughts on this?
I'm not a kernel hacker, but I've got some thoughts on this:
1 Modules (with the autoloader) can do that for anything not necessary to
Followup to: [EMAIL PROTECTED]
By author:"Heusden, Folkert van" [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
Would anyone be intrested (besides me) in a kernel which can page
out certain parts of itself? The kernel should be in some kind of
vmlinux-ish (as in: uncompressed) format on
H. Peter Anvin writes:
By author:"Heusden, Folkert van" [EMAIL PROTECTED]
Would anyone be intrested (besides me) in a kernel which can page
...
Certain parts of drivers could get the __pageable prefix or so
VMS does this. It at least used to have a great tendency to crash
itself,
20 matches
Mail list logo
