search for: min_free_kbytes

Hi, what would be a good value for /proc/sys/vm/min_free_kbytes on a Dual-CPU EM64T System with 8 GB of memory. Kernel is 2.6.9-42.0.3.ELsmp. I know that the default might be a bit low. Unfortunatelly the documentation is a bit weak in this area. We are experiencing responsiveness problems (and higher than expected load) when the system is under combined me...

...s does not want to start permanently and I have to reinstall/restore it. This problem comes for me randomly, but maybe there is a trigger. I''ve tried to follow: http://xen.1045712.n5.nabble.com/2-6-32-27-dom0-BUG-unable-to-handle-kernel-paging-request-td3323011.html and raise /proc/sys/vm/min_free_kbytes, but it did not help. System info: Debian, Linux dom0 3.2.0-0.bpo.3-amd64 i libxenstore3.0 4.0.1-5.4 Xenstore communications library for Xen ii xen-hypervisor-4.0-amd64 4.0.1-5.4 The Xen Hypervisor on AMD64 ii xen-linux-system-3.2.0-0.bpo.3-amd64 3.2.23-1~bpo60+2 Xen system with Linux 3.2 on 64-b...

...rface for that. alloc_pages(GFP_NOWAIT, MAX_ORDER -1). > So why do we need any array based interface? Yes, I'm trying to get free pages directly via alloc_pages, so there will be no new mm APIs. I plan to let free page allocation stop when the remaining system free memory becomes close to min_free_kbytes (prevent swapping). Best, Wei

...rface for that. alloc_pages(GFP_NOWAIT, MAX_ORDER -1). > So why do we need any array based interface? Yes, I'm trying to get free pages directly via alloc_pages, so there will be no new mm APIs. I plan to let free page allocation stop when the remaining system free memory becomes close to min_free_kbytes (prevent swapping). Best, Wei

...I assume you only want to balloon only memory directly > usable by the kernel so it will be > (GFP_KERNEL | __GFP_NOWARN) & ~__GFP_RECLAIM Sounds good to me, thanks. > > > I plan to let free page allocation stop when the remaining system free > > memory becomes close to min_free_kbytes (prevent swapping). > > ~__GFP_RECLAIM will make sure you are allocate as long as there is any > memory without reclaim. It will not even poke the kswapd to do the > background work. So I do not think you would need much more than that. "close to min_free_kbytes" - I meant w...

...s does not want to start permanently and I have to reinstall/restore it. This problem comes for me randomly, but maybe there is a trigger. I''ve tried to follow: http://xen.1045712.n5.nabble.com/2-6-32-27-dom0-BUG-unable-to-handle-kernel-paging-request-td3323011.html and raise /proc/sys/vm/min_free_kbytes, but it did not help. System info: Debian, Linux dom0 3.2.0-0.bpo.3-amd64 i libxenstore3.0 4.0.1-5.4 Xenstore communications library for Xen ii xen-hypervisor-4.0-amd64 4.0.1-5.4 The Xen Hypervisor on AMD64 ii xen-linux-sys...

...cache. As a side effect, i see that "Buffers" in /proc/meminfo grows up and sometimes smbd process is killed and respawned. I was wondering if anybody was able to successfully limit the page cache (with no side affects). Ofcourse i can drop caches using /proc/sys/vm/drop_caches and tweak min_free_kbytes but this is not my current intention. Any pointers to achieve this would be greatly appreciated. I hope this is right mailing list for the query. Please help me to find right mailing list in case i am mistaken. Cheers Ajay

I have set up Mailman on a virtual private server from 1and1 running Centos, though I can't tell which version. The system has 2 GB of memory. Mailman is receiving posts, but it is not sending them out to everybody. It is also getting some out-of-memory errors. The server is also runing Plesk for Web hosting. Something on the server is leaking memory. When first booted it has nearly 1.5

...ree of errors. NFS servers used dual bonded gigabit links in balance-alb mode. Turning off one interface in the bond made no difference. Relevant /etc/sysctl.conf parameters: vm.dirty_ratio = 50 vm.dirty_background_ratio = 1 vm.dirty_expire_centisecs = 1000 vm.dirty_writeback_centisecs = 100 vm.min_free_kbytes = 65536 net.core.rmem_default = 262144 net.core.rmem_max = 262144 net.core.wmem_default = 262144 net.core.wmem_max = 262144 net.core.netdev_max_backlog = 25000 net.ipv4.tcp_reordering = 127 net.ipv4.tcp_rmem = 4096 87380 16777216 net.ipv4.tcp_wmem = 4096 65536 16777216 net.ipv4.tcp_max_syn_backlog...

Hi, We''re setting up fairly large Lustre 2.1.2 filesystems, each with 18 nodes and 159 resources all in one Corosync/Pacemaker cluster as suggested by our vendor. We''re getting mixed messages on how large of a Corosync/Pacemaker cluster will work well between our vendor an others. 1. Are there Lustre Corosync/Pacemaker clusters out there of this size or larger? 2.

...mple. In fact you would need a more complex gfp mask. I assume you only want to balloon only memory directly usable by the kernel so it will be (GFP_KERNEL | __GFP_NOWARN) & ~__GFP_RECLAIM > I plan to let free page allocation stop when the remaining system free > memory becomes close to min_free_kbytes (prevent swapping). ~__GFP_RECLAIM will make sure you are allocate as long as there is any memory without reclaim. It will not even poke the kswapd to do the background work. So I do not think you would need much more than that. But let me note that I am not really convinced how this (or previous...

On a busy NFS server I've started receiving the following error messages and the system hangs with high load but no work being done. The system is a Dell R510 with 12 x 3TB drives in a RAID-50 configuration. The RAID-50 device is a full disk LVM (no partitions) and one large (36TB) data volume and the system is running CentOS 6.4 fully patched for OS and firmware. Anyone have any hints as

I have several CentOS5 hosts in a VMware ESX 3.5.0 226117 environment using iSCSI storage. Recently we've begun to experience journal aborts resulting in remounted-read-only filesystems as well as other filesystem issues - I can unmount a filesystem and force a check with "fsck -f" and occasionally find errors. I've found -

Hi, On 03/19/2018 03:42 PM, TomK wrote: > On 3/19/2018 5:42 AM, Ondrej Valousek wrote: > Removing NFS or NFS Ganesha from the equation, not very impressed on my > own setup either.? For the writes it's doing, that's alot of CPU usage > in top. Seems bottle-necked via a single execution core somewhere trying > to facilitate read / writes to the other bricks. > >

On Tue, Jul 10, 2018 at 6:24 PM Wei Wang <wei.w.wang at intel.com> wrote: > > We only get addresses of the "MAX_ORDER-1" blocks into the array. The > max size of the array that could be allocated by kmalloc is > KMALLOC_MAX_SIZE (i.e. 4MB on x86). With that max array, we could load > "4MB / sizeof(u64)" addresses of "MAX_ORDER-1" blocks, that is,

On Tue, Jul 10, 2018 at 6:24 PM Wei Wang <wei.w.wang at intel.com> wrote: > > We only get addresses of the "MAX_ORDER-1" blocks into the array. The > max size of the array that could be allocated by kmalloc is > KMALLOC_MAX_SIZE (i.e. 4MB on x86). With that max array, we could load > "4MB / sizeof(u64)" addresses of "MAX_ORDER-1" blocks, that is,

Hi Maby stupid question :) It possible to have 3 directors (frontend) but without rings ? All directors connect to this same dovecot (backend) - all backad have this same login_trusted_networks -- Maciej Mi?aszewski IQ PL Sp. z o.o. Starszy Administrator Systemowy

..._expire_centisecs = 3000 vm.dirty_ratio = 20 vm.dirty_writeback_centisecs = 500 vm.drop_caches = 0 vm.highmem_is_dirtyable = 0 vm.hugepages_treat_as_movable = 0 vm.hugetlb_shm_group = 0 vm.laptop_mode = 0 vm.legacy_va_layout = 0 vm.lowmem_reserve_ratio = 256 32 32 vm.max_map_count = 65530 vm.min_free_kbytes = 3084 vm.mmap_min_addr = 4096 vm.nr_hugepages = 0 vm.nr_overcommit_hugepages = 0 vm.nr_pdflush_threads = 0 vm.overcommit_memory = 0 vm.overcommit_ratio = 50 vm.page-cluster = 3 vm.percpu_pagelist_fraction = 0 vm.scan_unevictable_pages = 0 vm.stat_interval = 1 vm.swappiness = 30 vm.user_reserve_kby...

hi xen 4.0.1 w/2.6.32.41 Last week dom0 experienced an hard crash and box need to be restarted manually (despite kernel.panic=20). Serial console was not setup, only netconsole. No relevant entries through netconsole, but analyzing logs I see some crashes twenty minutes before fatal hang. Dec 2 01:29:39 xenhost-rack1 kernel: [4437064.011963] Call Trace: Dec 2 01:29:39 xenhost-rack1 kernel: