mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven French <sfrench@us.ibm.com>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cifs leaks memory like crazy in 2.5.61
Date: Thu, 20 Feb 2003 10:28:07 -0600	[thread overview]
Message-ID: <OF566C3F49.C8CA5594-ON87256CD3.0058B0B3@us.ibm.com> (raw)





Hadn't run into this - I had been focusing on the readahead and write page
improvements (which have improved especially write performance
spectacularly) and also have just fixed a problem with redundant lookups of
directory inodes but had not been doing readdir (cifs
Trans2FindFirst/Trans2FindNext) testing recently.  I just did - and the
situation looks worse than you describe and probably related to what you
are running into. I found a readdir test case that hangs my post 2.5.62
system pretty fast and the last two unrelated cifs changesets don't fix it.
The cifs readdir code needed some rework anyway - I will crawl through it
today.  Thanks for finding this.

>kmem_cache_destroy: Can't free all objects e8eefd00
>cifs_destroy_request_cache: error not all structures were freed
>
>Is this a known problem?

Steve French
Senior Software Engineer
Linux Technology Center - IBM Austin
phone: 512-838-2294
email: sfrench@us.ibm.com


             reply	other threads:[~2003-02-20 16:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 16:28 Steven French [this message]
2003-02-20 16:45 ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2003-02-20 21:21 Steven French
2003-02-20 16:56 Steven French
2003-02-20 17:16 ` Jeff Garzik
2003-02-20 13:28 Martin Josefsson

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=OF566C3F49.C8CA5594-ON87256CD3.0058B0B3@us.ibm.com \
    --to=sfrench@us.ibm.com \
    --cc=gandalf@wlug.westbo.se \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®