Re: Cleanup and untangling of kernel VM initialization

2013-03-08 Thread Konstantin Belousov
On Fri, Mar 08, 2013 at 01:58:38PM +0100, Andre Oppermann wrote: > On 08.03.2013 10:16, Konstantin Belousov wrote: > > On Thu, Mar 07, 2013 at 06:03:51PM +0100, Andre Oppermann wrote: > >>pager_map: is used for pager IO to a storage media (disk). Not > >>pageable. Calculation: MAXPHYS * min

Re: Cleanup and untangling of kernel VM initialization

2013-03-08 Thread Alan Cox
On 03/08/2013 06:58, Andre Oppermann wrote: > On 08.03.2013 10:16, Konstantin Belousov wrote: >> On Thu, Mar 07, 2013 at 06:03:51PM +0100, Andre Oppermann wrote: >>>pager_map: is used for pager IO to a storage media (disk). Not >>>pageable. Calculation: MAXPHYS * min(max(nbuf/4, 16), 256).

Re: Cleanup and untangling of kernel VM initialization

2013-03-08 Thread Andre Oppermann
On 08.03.2013 10:16, Konstantin Belousov wrote: On Thu, Mar 07, 2013 at 06:03:51PM +0100, Andre Oppermann wrote: pager_map: is used for pager IO to a storage media (disk). Not pageable. Calculation: MAXPHYS * min(max(nbuf/4, 16), 256). > It is more versatile. The space is used for pbufs,

Re: Cleanup and untangling of kernel VM initialization

2013-03-08 Thread Konstantin Belousov
On Thu, Mar 07, 2013 at 06:03:51PM +0100, Andre Oppermann wrote: > On 01.02.2013 18:09, Alan Cox wrote: > > On 02/01/2013 07:25, Andre Oppermann wrote: > >> Rebase auto-sizing of limits on the available KVM/kmem_map instead of > >> physical > >> memory. Depending on the kernel and architecture

Re: Cleanup and untangling of kernel VM initialization

2013-03-07 Thread Andre Oppermann
On 01.02.2013 18:09, Alan Cox wrote: On 02/01/2013 07:25, Andre Oppermann wrote: Rebase auto-sizing of limits on the available KVM/kmem_map instead of physical memory. Depending on the kernel and architecture configuration these two can be very different. Comments and reviews appreciated

Re: Cleanup and untangling of kernel VM initialization

2013-02-01 Thread Alan Cox
On 02/01/2013 07:25, Andre Oppermann wrote: > As an outcome of the recent problems with auto-sizing and auto-tuning of > the various kernel subsystems and related memory structures I've taken a > closer look at the whole KVM inner working and initialization process. > > I've found the VM and KVM in

Cleanup and untangling of kernel VM initialization

2013-02-01 Thread Andre Oppermann
As an outcome of the recent problems with auto-sizing and auto-tuning of the various kernel subsystems and related memory structures I've taken a closer look at the whole KVM inner working and initialization process. I've found the VM and KVM initialization to be somewhat obscure and stuck half-w