From: Jeff Garzik <jgarzik@pobox.com>
To: Steven French <sfrench@us.ibm.com>
Cc: Martin Josefsson <gandalf@wlug.westbo.se>, linux-kernel@vger.kernel.org
Subject: Re: cifs leaks memory like crazy in 2.5.61
Date: Thu, 20 Feb 2003 11:45:47 -0500 [thread overview]
Message-ID: <20030220164547.GB9800@gtf.org> (raw)
In-Reply-To: <OF566C3F49.C8CA5594-ON87256CD3.0058B0B3@us.ibm.com>
On Thu, Feb 20, 2003 at 10:28:07AM -0600, Steven French wrote:
> 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
Well, here is a humble request to actually test your stuff,
before adding more features!
Jeff
next prev parent reply other threads:[~2003-02-20 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 16:28 cifs leaks memory like crazy in 2.5.61 Steven French
2003-02-20 16:45 ` Jeff Garzik [this message]
-- 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=20030220164547.GB9800@gtf.org \
--to=jgarzik@pobox.com \
--cc=gandalf@wlug.westbo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.