From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 04/13] mm: new shrinker API Date: Tue, 23 Aug 2011 05:15:29 -0400 Message-ID: <20110823091529.GC21492@infradead.org> References: <1314089786-20535-1-git-send-email-david@fromorbit.com> <1314089786-20535-5-git-send-email-david@fromorbit.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, khlebnikov@openvz.org To: Dave Chinner Return-path: Received: from 173-166-109-252-newengland.hfc.comcastbusiness.net ([173.166.109.252]:41778 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754128Ab1HWJPa (ORCPT ); Tue, 23 Aug 2011 05:15:30 -0400 Content-Disposition: inline In-Reply-To: <1314089786-20535-5-git-send-email-david@fromorbit.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: > /* > * A callback you can register to apply pressure to ageable caches. It's much more than just a single callback these days. > + * @scan_objects will be made from the current reclaim context. > */ > struct shrinker { > int (*shrink)(struct shrinker *, struct shrink_control *sc); > + long (*count_objects)(struct shrinker *, struct shrink_control *sc); > + long (*scan_objects)(struct shrinker *, struct shrink_control *sc); Is shrink_object really such a good name for this method?