Rik van Riel wrote:
> On Fri, 27 Apr 2001, LA Walsh wrote:
> > An interesting option (though with less-than-stellar performance
> > characteristics) would be a dynamically expanding swapfile. If you're
> > going to be hit with swap penalties, it may be useful to not have to
> > pre-reserve something you only hit once in a great while.
> This makes amazingly little sense since you'd still need to
> pre-reserve the disk space the swapfile grows into.
> A dynamically growing swap file can only save you if you
> reserve enough free space on your filesystem for the thing
> to grow...
I seams to work for M$, not that they are a good example.
But in /proc/sys/vm or /proc/sys/swapfile having
min_swap, max_swap, min_free_space and the filename to use. This could
then be set by init scripts like sysctl.
It never grows larger than max(swapfile.max_swap, free_space -
so if you have free space on the filesystem it can be used,
but if you don't have space the current behavior remains.
Sure it would be slow, but that would only be a problem if you
run out of swap space and need to allocate more. Any
time this routine allocates a larger file than syapfile.min_swap
or frees space you send a WARN message.
Now the user will know why the performance dropped
and can either add RAM, or increase swap with by
partition, file, or increase swapfile.min_swap.
Those with enough RAM/swap will never even know it's there.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 30 2001 - 21:00:19 EST