Re: HEADSUP: UMA not reentrant / possible memory leak

From: Bosko Milekic (bmilekic_at_technokratis.com)
Date: 07/30/03

  • Next message: Robert Watson: "Re: STEP 2, fixing dhclient behaviour with multiple interfaces"
    Date: Wed, 30 Jul 2003 09:11:47 +0000
    To: Jeff Roberson <jroberson@chesapeake.net>
    
    

    On Tue, Jul 29, 2003 at 11:42:51PM -0400, Jeff Roberson wrote:
    > On Wed, 30 Jul 2003 Tor.Egge@cvsup.no.freebsd.org wrote:
    >
    > > > The indication of this is that the g_bio zone does not return to
    > > > zero USED as it should.
    > >
    > > It looks like z->uz_cachefree is slightly out of date (updated in
    > > zone_timout() every 20th second) and often too low (not taking the
    > > z->uz_full_bucket list into account).
    > >
    > > The enclosed patch recalculates the number of free elements on the
    > > buckets instead of using z->uz_cachefree.
    > >
    >
    > I definitely like this patch. If it works would you please commit it?
    > There are other issues for sure though. UMA can leak pages from zones
    > when they are destroyed. I'm going to look into this asap.
    >
    > Cheers,
    > Jeff

      Tor's patch does address the problem of having to account for the
      buckets in the zone as well (besides for just the pcpu cache buckets).
      So if it does get committed, can the calculation of uz_cachefree from
      the timer routine be axed in the same change, as it is no longer
      significant?

    -- 
    Bosko Milekic  *  bmilekic@technokratis.com  *  bmilekic@FreeBSD.org
    TECHNOkRATIS Consulting Services  *  http://www.technokratis.com/
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    

  • Next message: Robert Watson: "Re: STEP 2, fixing dhclient behaviour with multiple interfaces"

    Relevant Pages

    • Re: NEWBUS states
      ... :>: I think the right fix here is to maintain in sync devinfo.h and bus.h ... Obviously that is not a finished patch, ... I'm specifically suggesting that we only MFC ... that would mean to not commit a patch and make impossible a future ...
      (freebsd-arch)
    • Re: [GIT PATCH] another tranche of SCSI updates for 2.6.26
      ... commit 064922a805ec7aadfafdd27aa6b4908d737c3c1d ... This patch adds more const keywords where appropriate. ... fix SLUB WARN_ON ... KVM: SVM: remove now obsolete FIXME comment ...
      (Linux-Kernel)
    • Re: Impact: (was Re: [PATCH] update rwlock initialization for nat_table)
      ... The commit e099a173573ce1ba171092aee7bb3c72ea686e59 ... As Andrew mentioned this is a bug (albeit a "nano-bug" as you ... hard to describe the practical impact of a patch in a single line, ... Try it if you dont believe me;-) In ...
      (Linux-Kernel)
    • Re: [Bug #14141] order 2 page allocation failures in iwlagn
      ... *only* printed when the RX buffers are really low. ... that patch triggers them in the extreme swap situation. ... but could not find an obvious candidate within the page allocator itself which ... this driver and I think we have the problem commit there. ...
      (Linux-Kernel)
    • Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
      ... MAINTAINERS information, we have 3 options: ... There are things git can help, and other things git does not ... Linus already gave a script to grep *-by: lines from commit ... integration to git-based patch flow. ...
      (Linux-Kernel)