linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Sharpe <rsharpe@richardsharpe.com>
To: Volker Lendecke <Volker.Lendecke@SerNet.DE>
Cc: Theodore Tso <tytso@MIT.EDU>, Andreas Dilger <adilger@sun.com>,
	samba-technical@samba.org,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-cifs-client@lists.samba.org, Jeremy Allison <jra@samba.org>
Subject: Re: Samba speed
Date: Tue, 9 Dec 2008 07:40:27 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0812090737460.14431@durable> (raw)
In-Reply-To: <E1L9xMu-00D9F1-TU@intern.SerNet.DE>

On Tue, 9 Dec 2008, Volker Lendecke wrote:

>> Is there a maximum stride size used by the redirector?  i.e., will it
>> use something bigger than 128k?  In any case, increasing the ext3
>> reservation window size should still be helpful.  It's OK if we
>> increase it to 32 blocks (128k, on a 4k block filesystem), and the
>> stride size is smaller than that.  But if it is often bigger than
>> 128k, then then it would probably be better if samba used the
>> EXT3_IOC_SETRSVSZ ioctl to dynamically set the reservation size as
>> appropriate.
>
> One might try to use "dd" from Cygwin on Windows. When I
> once analyzed this behaviour, the 1-byte writes were exactly
> at the end of the block the Win32 app gave to the kernel as
> seen by the sysinternals filemon tool.

Hmmm, I always thought the network behavior was to prevent the app from 
being given an ENOSPACE error when it closed the file and the OS tried to 
flush the cache only to find that there was no space remaining on the 
remote file system to actually perform the writes the local cache 
accepted.

However, this suggests that the behavior is the same for local and remote 
file systems.

I do believe, as Ronnie said and as your evidence suggests, that these 
writes are at the end of the IO written into the cache by the app.

Regards
-------
Richard Sharpe, rsharpe[at]richardsharpe.com, rsharpe[at]samba.org,
sharpe[at]ethereal.com, http://www.richardsharpe.com


      reply	other threads:[~2008-12-09 15:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 18:21 Samba speed Jeremy Allison
2008-12-08 22:39 ` Theodore Tso
2008-12-08 23:12   ` Jeremy Allison
2008-12-08 23:38     ` Theodore Tso
2008-12-09  0:37       ` Andreas Dilger
2008-12-09  6:06         ` Theodore Tso
2008-12-09  6:25           ` ronnie sahlberg
2008-12-09  6:55             ` Theodore Tso
2008-12-09  7:50               ` Volker Lendecke
2008-12-09 15:40                 ` Richard Sharpe [this message]

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=Pine.LNX.4.63.0812090737460.14431@durable \
    --to=rsharpe@richardsharpe.com \
    --cc=Volker.Lendecke@SerNet.DE \
    --cc=adilger@sun.com \
    --cc=jra@samba.org \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=samba-technical@samba.org \
    --cc=tytso@MIT.EDU \
    /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;
as well as URLs for NNTP newsgroup(s).