public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman@suse.de>
To: "\"J.A. Magallón\"" <jamagallon@ono.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: CIFS is slooow, gvfs is fast
Date: Fri, 22 Oct 2010 16:14:46 +0530	[thread overview]
Message-ID: <4CC16B1E.4060709@suse.de> (raw)
In-Reply-To: <20101022013544.0fdab0e0@werewolf.home>

(Cc linux-cifs@vger.kernel.org)

On 10/22/2010 05:05 AM, J.A. Magallón wrote:

> I have a very strange behaviour with windows networking.
> I have an HTPC, which I access from my Linux desktop. It runs Windows 7.
> Network is GigaBit, routed by a Linksys WRT320N running latest DD-WRT.
> I setup an automount path under /net/htpc with CIFS filesystem.
> I can also access the drives in HTPC via gvfs from Gnome DE.
> 
> Problem: speed is _VERY_ different.
> R/W through the automount point (CIFS fs), is roughly 7-8 MB/s (ridiculous
> for gigabit speeds).
> R/W through Gnome/gvfs (kind of fuse) goes around 35 - 40 MB/s (400 Mbits/s),
> that look much better.

What is the kernel version In which you are seeing the problem? I'm not
seeing this on 2.6.36-rc4. Do you have a wired interface as well? Are
you sure that both are using the same network path?

> I have tried with different rsize/wsize in mount, but speed is the same
> (perhaps I did not get the right values...).

Does the changes reflect in /proc/mounts?


-- 
Suresh Jayaraman

  reply	other threads:[~2010-10-22 10:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21 23:35 CIFS is slooow, gvfs is fast J.A. Magallón
2010-10-22 10:44 ` Suresh Jayaraman [this message]
2010-10-22 16:06   ` Steve French
2010-10-22 22:46   ` J.A. Magallón
2010-10-23 23:30     ` J.A. Magallón
2010-10-25 10:14       ` Suresh Jayaraman
2010-10-29 22:33         ` J.A. Magallón
2010-10-30  0:54           ` Steve French

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=4CC16B1E.4060709@suse.de \
    --to=sjayaraman@suse.de \
    --cc=jamagallon@ono.com \
    --cc=linux-cifs@vger.kernel.org \
    --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