From: bert hubert <ahu@ds9a.nl>
To: Steve French <smfrench@austin.rr.com>
Cc: linux-kernel@vger.kernel.org, linux-cifs-client@lists.samba.org,
samba-technical@lists.samba.org
Subject: Re: cifs large write performance improvements to Samba
Date: Mon, 13 Dec 2004 15:38:31 +0100 [thread overview]
Message-ID: <20041213143831.GA3743@outpost.ds9a.nl> (raw)
In-Reply-To: <1102916738.5937.48.camel@smfhome.smfdom>
On Sun, Dec 12, 2004 at 11:45:38PM -0600, Steve French wrote:
> Running with a faster processor (otherwise the same) this improved to
> 19.3 seconds average (and using the even larger 120K write size
> performance dropped slightly to 20.6 seconds)
While this is all supremely cool, my inbox has several reactions from cifs
users about my never addressed query [1] on linux-cifs-clients regarding memory
leaks you can drive a truck through in cifs.
[1] http://marc.theaimsgroup.com/?l=linux-cifs-client&m=109221678006861&w=2
I'd love to deploy cifs and I've recommended it to many people, they've all
switched back to smbfs!
Now while I fully understand open source ethics (breaks, both pieces etc),
I'd really hope cifs would shape up in terms of ""enterprise reliability"".
Anything I can do to help, let me know. The referred URL contains some of my
conclusions at the time.
Thanks.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-12-13 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 5:45 cifs large write performance improvements to Samba Steve French
2004-12-13 14:38 ` bert hubert [this message]
[not found] ` <41BDC911.9010600@austin.rr.com>
2004-12-22 14:56 ` bert hubert
-- strict thread matches above, loose matches on Subject: below --
2004-12-13 16:56 Steve French
2004-12-13 17:20 ` cliff white
2004-12-13 18:34 ` Steve French
2004-12-13 18:43 ` Steve French
2004-12-16 12:11 ` Marcelo Tosatti
2004-12-16 18:58 ` Hans Reiser
2004-12-16 16:30 ` Marcelo Tosatti
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=20041213143831.GA3743@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@austin.rr.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.