search for: iterate_sup

...move the page cache to the hypervisor, e.g., using emulated NVDIMMs or virtio-pmem. > Would it be possible?to add a mechanism that explicitly causes page > cache to shrink without requiring the system to be under memory pressure? > We do have a sysctl "drop_caches" which calls iterate_supers(drop_pagecache_sb, NULL) and drop_slab(). doc/Documentation/sysctl/vm.txt: ============================================================== drop_caches Writing to this will cause the kernel to drop clean caches, as well as reclaimable slab objects like dentries and inodes. Once dropped, their...

...1b4fc0>] ? fdatawrite_one_bdev+0x20/0x20 [ 386.319840] [<ffffffff8169d0bd>] wait_for_completion+0x1d/0x20 [ 386.319847] [<ffffffff811ad907>] sync_inodes_sb+0x97/0xd0 [ 386.319854] [<ffffffff811b4fdd>] sync_inodes_one_sb+0x1d/0x30 [ 386.319862] [<ffffffff811894a1>] iterate_supers+0x101/0x110 [ 386.319867] [<ffffffff811b5145>] sys_sync+0x35/0x90 [ 386.319874] [<ffffffff816a686d>] system_call_fastpath+0x1a/0x1f [ 386.319881] Sched Debug Version: v0.10, 3.6.0-030600rc5-generic #201209082035 [ 386.319885] ktime : 386839.691...

On Fri, Oct 04, 2019 at 10:06:03AM +0200, David Hildenbrand wrote: > On 04.10.19 01:15, Tyler Sanderson wrote: > > I was mistaken, the problem with overcommit accounting is not fixed by > > the change to shrinker interface. > > This means that large allocations are stopped even if they could succeed > > by deflating the balloon. > > Please note that some people

On Fri, Oct 04, 2019 at 10:06:03AM +0200, David Hildenbrand wrote: > On 04.10.19 01:15, Tyler Sanderson wrote: > > I was mistaken, the problem with overcommit accounting is not fixed by > > the change to shrinker interface. > > This means that large allocations are stopped even if they could succeed > > by deflating the balloon. > > Please note that some people

This reverts commit 5500cdbe14d7435e04f66ff3cfb8ecd8b8e44ebf. We had numerous reports of premature ENOSPC that were bisected to this patch. Reverting will not break things but a warning in ''use_block_rsv'' may show up in the syslog. There''s no alternative fix in sight and the ENOSPC problem affects all 3.3 btrfs users during normal filesystem use. CC:

...62/0x66 [btrfs] Jun 10 14:57:17 mithrandir kernel: [ 266.182639] [<ffffffff810d13c2>] __sync_filesystem+0x5e/0x72 Jun 10 14:57:17 mithrandir kernel: [ 266.182686] [<ffffffff810d13e7>] sync_one_sb+0x11/0x13 Jun 10 14:57:17 mithrandir kernel: [ 266.182730] [<ffffffff810b49ec>] iterate_supers+0x6a/0xbf Jun 10 14:57:17 mithrandir kernel: [ 266.182775] [<ffffffff810d146e>] sys_sync+0x3d/0x4f Jun 10 14:57:17 mithrandir kernel: [ 266.182816] [<ffffffff8139f03b>] system_call_fastpath+0x16/0x1b Jun 10 14:57:17 mithrandir kernel: [ 266.182864] Code: ff ff 48 8b 80 38 e0 ff...

Hello On my HP Compaq dc5800 with Ubuntu 13.04 and their 3.8.0-19-lowlatency kernel, I''ve got quite some kernel traces in the syslog. You can find them below or at http://pastebin.com/bLXPBX67 (to avoid line breaks…). These kernel traces all begin with: WARNING: at fs/btrfs/free-space-cache.c:921 __btrfs_write_out_cache+0x6b9/0x9a0 [btrfs]() Most of the time, it starts with: Call

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-rfc-v4 The basic idea of virtio-mem is to provide a flexible, cross-architecture memory hot(un)plug solution that avoids many limitations imposed by existing technologies, architectures, and interfaces. More details can be found below and in linked material. This

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-rfc-v4 The basic idea of virtio-mem is to provide a flexible, cross-architecture memory hot(un)plug solution that avoids many limitations imposed by existing technologies, architectures, and interfaces. More details can be found below and in linked material. This