Re: [Regression bisected] btrfs: always wait on ordered extents at fsync time

2018-11-09 Thread Mel Gorman
On Fri, Nov 09, 2018 at 09:51:48PM +, Mel Gorman wrote: > Unfortunately, as > I'm about to travel, I didn't attempt a revert and a test comparing 4.18, > 4.19 and 4.20-rc1 is a few hours away so this could potentially be fixed > already but I didn't spot any obvi

[Regression bisected] btrfs: always wait on ordered extents at fsync time

2018-11-09 Thread Mel Gorman
9ff08a456e3e1 scaled 6611+-130 sigma 6347 actual 6611.04+-130.44 Hmean-new_dbase-5 impera::Fri 9 Nov 20:34:41 GMT 2018::reaim delboy :bad: b5e6c3e170b77025b5f6174258c7ad71eed2d4de scaled 4272+-90 sigma 6347 actual 4272.68+-90.93 Hmean-new_dbase-5 impera::Fri 9 Nov 20:57:11 GMT 2018::reaim delboy :good: 16d1c062c7de2999ea7be61d31070fa4ce3d99c4 scaled 6541+-556 sigma 6347 actual 6541.07+-556.74 Hmean-new_dbase-5 -- Mel Gorman SUSE Labs

Re: [ANNOUNCE] fsperf: a simple fs/block performance testing framework

2017-10-10 Thread Mel Gorman
ora and debian but the mappings are not up-to-date as I do not personally run those distributions. Even with the quality-of-implementation issues, it seems to me that it covers a lot of the requirements that fsperf aims for. -- Mel Gorman SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [RFC PATCH] mm, memcg: fix (Re: OOM: Better, but still there on)

2016-12-30 Thread Mel Gorman
On Fri, Dec 30, 2016 at 12:05:45PM +0100, Michal Hocko wrote: > On Fri 30-12-16 10:19:26, Mel Gorman wrote: > > On Mon, Dec 26, 2016 at 01:48:40PM +0100, Michal Hocko wrote: > > > On Fri 23-12-16 23:26:00, Nils Holland wrote: > > > > On Fri, Dec 23, 2016 at 03:47:

Re: [RFC PATCH] mm, memcg: fix (Re: OOM: Better, but still there on)

2016-12-30 Thread Mel Gorman
with 4.8 kernels > I think it's unfortunate that per-zone stats are reintroduced to the memcg structure. I can't help but think that it would have also worked to always rotate a small number of pages if !inactive_list_is_low and reclaiming for memcg even if it distorted page agi

btrfs deadlocks under stress up until 3.12

2013-12-04 Thread Mel Gorman
ere are a number of deadlock-related fixes merged for btrfs between 3.11 and 3.12. Are there plans to backport them? -- Mel Gorman SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More major

Re: [patch 5/5] Btrfs: pass __GFP_WRITE for buffered write page allocations

2011-10-03 Thread Mel Gorman
On Fri, Sep 30, 2011 at 09:17:24AM +0200, Johannes Weiner wrote: > Tell the page allocator that pages allocated for a buffered write are > expected to become dirty soon. > > Signed-off-by: Johannes Weiner > Reviewed-by: Rik van Riel Acked-by: Mel Gorman -- Mel Gorman

Re: [patch 1/5] mm: exclude reserved pages from dirtyable memory

2011-10-03 Thread Mel Gorman
per-zone level, where the distance between reclaim and the dirty pages > is mostly much smaller in absolute numbers. > > Signed-off-by: Johannes Weiner > Reviewed-by: Rik van Riel Acked-by: Mel Gorman -- Mel Gorman SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [patch 2/2/4] mm: try to distribute dirty pages fairly across zones

2011-09-28 Thread Mel Gorman
onsidered zones is allowed to ignore > the dirty limits before going into direct reclaim or even failing the > allocation, until a future patch changes the global dirty throttling > and flusher thread activation so that they take individual zone states > into account. > > Si

Re: [patch 1/2/4] mm: writeback: cleanups in preparation for per-zone dirty limits

2011-09-28 Thread Mel Gorman
; their relationship is more apparent and that they can be commented on > as a group. > > Signed-off-by: Johannes Weiner Acked-by: Mel Gorman -- Mel Gorman SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [patch 1/4] mm: exclude reserved pages from dirtyable memory

2011-09-22 Thread Mel Gorman
On Thu, Sep 22, 2011 at 11:03:26AM +0200, Johannes Weiner wrote: > On Wed, Sep 21, 2011 at 04:03:28PM +0100, Mel Gorman wrote: > > On Wed, Sep 21, 2011 at 03:04:23PM +0100, Mel Gorman wrote: > > > On Tue, Sep 20, 2011 at 03:45:12PM +0200, Johannes Weiner wrote: > > >

Re: [patch 1/4] mm: exclude reserved pages from dirtyable memory

2011-09-21 Thread Mel Gorman
On Wed, Sep 21, 2011 at 03:04:23PM +0100, Mel Gorman wrote: > On Tue, Sep 20, 2011 at 03:45:12PM +0200, Johannes Weiner wrote: > > The amount of dirtyable pages should not include the total number of > > free pages: there is a number of reserved pages that the page > > alloca

Re: [patch 3/4] mm: filemap: pass __GFP_WRITE from grab_cache_page_write_begin()

2011-09-21 Thread Mel Gorman
On Tue, Sep 20, 2011 at 03:45:14PM +0200, Johannes Weiner wrote: > Tell the page allocator that pages allocated through > grab_cache_page_write_begin() are expected to become dirty soon. > > Signed-off-by: Johannes Weiner Acked-by: Mel Gorman -- Mel Gorman SUSE Labs -- To unsu

Re: [patch 2/4] mm: writeback: distribute write pages across allowable zones

2011-09-21 Thread Mel Gorman
lower zones. As it is, the reader is required to remember that this affects LRU ordering and when/if reclaim tries to write back the page. > + if (!(alloc_flags & ALLOC_SLOWPATH) && > + (gfp_mask & __GFP_WRITE) && !zone_dirty_ok(zone)) >

Re: [patch 1/4] mm: exclude reserved pages from dirtyable memory

2011-09-21 Thread Mel Gorman
irtyable_memory(x); > diff --git a/mm/page_alloc.c b/mm/page_alloc.c > index 1dba05e..7e8e2ee 100644 > --- a/mm/page_alloc.c > +++ b/mm/page_alloc.c > @@ -5075,6 +5075,7 @@ static void calculate_totalreserve_pages(void) > > if (max > zone->present_pages) >