From: Ben Myers <bpm@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/7] xfs: use a normal shrinker for the dquot freelist
Date: Thu, 9 Feb 2012 17:13:46 -0600 [thread overview]
Message-ID: <20120209231346.GM7762@sgi.com> (raw)
In-Reply-To: <20120209225626.GA844@infradead.org>
Hey Christoph,
On Thu, Feb 09, 2012 at 05:56:26PM -0500, Christoph Hellwig wrote:
> On Thu, Feb 09, 2012 at 04:03:20PM -0600, Ben Myers wrote:
> > I've been messing with this and haven't gotten it to call us with
> > nr_to_scan other than 0 or -1 yet. Maybe I need more dquots.
> > (time passes) Ok, I have it going now. Comments below.
>
> To actually hit this I hade to use a VM with very little memory assigned
> to it, and then creat lots of dquots and causes memory pressure.
>
> I have about 20.000 users on it, and I did a quota report for all of
> them while catting one block device into another using buffered I/O.
Ah, I see.
> > > + LIST_HEAD (dispose_list);
> > > + struct xfs_dquot *dqp;
> > >
> > > - if (nfree <= ndqused && nfree < ndquot)
> > > + if ((sc->gfp_mask & (__GFP_FS|__GFP_WAIT)) != (__GFP_FS|__GFP_WAIT))
> > > return 0;
> > > + if (!nr_to_scan)
> > > + goto out;
> >
> > I suggest something more like:
> >
> > if (!nr_to_scan)
> > goto out;
> > if ((sc->gfp_mask...
> > return -1;
>
> Why? Counting the number of objects when we can't actually do anything
> is just a waste of time,
> and -1 vs 0 for the sizing pass seem to be
> treateds the same in the calling code.
That's a good point, but the shrinker interface has documented that
you're supposed to return -1 in this situation... and that you aren't
allowed to return -1 when nr_to_scan == 0.
> > > -
> > > - return B_TRUE;
> > > + while (!list_empty(&dispose_list)) {
> > > + dqp = list_first_entry(&dispose_list, struct xfs_dquot,
> > > + q_freelist);
> > > + list_del_init(&dqp->q_freelist);
> > > + xfs_qm_dqfree_one(dqp);
> > > + }
> > > +out:
> > > + return (xfs_Gqm->qm_dqfrlist_cnt / 100) * sysctl_vfs_cache_pressure;
> >
> > return atomic_read(&xfs_Gqm->qm_totaldquots);
> >
> > This works well for me and seems to be closer to the shrinker interface
> > as documented:
>
> It's pointless - we can only apply pressure to dquots that are on the
> freelist. No amount of shaking will allow us to reclaim a referenced
> dquot.
Sure... then it should be:
return atomic_read(&xfs_Gqm->qm_frlist_cnt);
What is the value of the additional calculation?
> > * The callback must not return -1 if nr_to_scan is zero.
>
> this is against your suggestion of using -1 for the estimation pass
> above, btw.
No it isn't... if nr_to_scan == 0 we would have jumped to 'out' and
returned the count.
Thanks,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-09 23:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 13:57 [PATCH 0/7] better dquot caching Christoph Hellwig
2012-02-01 13:57 ` [PATCH 1/7] xfs: use a normal shrinker for the dquot freelist Christoph Hellwig
2012-02-09 22:03 ` Ben Myers
2012-02-09 22:56 ` Christoph Hellwig
2012-02-09 23:13 ` Ben Myers [this message]
2012-02-10 1:52 ` Dave Chinner
2012-02-10 16:48 ` Ben Myers
2012-02-10 1:49 ` Dave Chinner
2012-02-10 16:56 ` Ben Myers
2012-02-01 13:57 ` [PATCH 2/7] xfs: per-filesystem dquot LRU lists Christoph Hellwig
2012-02-01 13:57 ` [PATCH 3/7] xfs: use per-filesystem radix trees for dquot lookup Christoph Hellwig
2012-02-01 13:57 ` [PATCH 4/7] xfs: remove the per-filesystem list of dquots Christoph Hellwig
2012-02-01 13:57 ` [PATCH 5/7] xfs: use per-cpu data for the quota statistics Christoph Hellwig
2012-02-01 13:57 ` [PATCH 6/7] xfs: user per-cpu stats for the total dquot numbers Christoph Hellwig
2012-02-01 13:57 ` [PATCH 7/7] xfs: remove the globalk xfs_Gqm structure Christoph Hellwig
2012-02-07 7:30 ` [PATCH 0/7] better dquot caching Ben Myers
2012-02-07 13:24 ` Christoph Hellwig
2012-02-07 15:23 ` Ben Myers
2012-02-11 20:13 ` Arkadiusz Miśkiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120209231346.GM7762@sgi.com \
--to=bpm@sgi.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox