From: Suresh Jayaraman <sjayaraman@suse.de>
To: "\"J.A. Magallón\"" <jamagallon@ono.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-cifs@vger.kernel.org
Subject: Re: CIFS is slooow, gvfs is fast
Date: Mon, 25 Oct 2010 15:44:44 +0530 [thread overview]
Message-ID: <4CC55894.5040509@suse.de> (raw)
In-Reply-To: <20101024013038.057442c0@werewolf.home>
On 10/24/2010 05:00 AM, J.A. Magallón wrote:
> On Sat, 23 Oct 2010 00:46:36 +0200, "J.A. Magall�n" <jamagallon@ono.com> wrote:
>
>>
>> If you mean hardware network path (cabling, router), yes.
>> For file paths, CIFS fs is under /net/htpc/media, and gvfs uses a mount
>> point on '~/.gvfs/media on htpc'.
>>
>> And here comes the weird part. To rule out the desktop environment factor,
>> I tried a dd in both paths. On /net, I get 16.6 MB/s, and on
>> ~/.gvfs/xxx, I just get 5.5 MB/s. I really don't understand anything...
>> things get reversed depending if you use a gui or commandline.
>>
>> Weird, really weird...
>>
>
> Well, to sort things out, I did some more tests (this does not mean things
> get any closer to be clear for me at least...).
>
> Can anybody tell me whats going here...??
> It looks just like gui tools behave just in reverse of cli, and that a plain
> smbclient is faster that cifs. I'm really confused...
>
Could you try mounting from commandline with something like
`mount -t cifs //server/share /mnt/point -o user=user1`
(commenting out the fstab entry) and try copying the file?
--
Suresh Jayaraman
next prev parent reply other threads:[~2010-10-25 10:14 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
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 [this message]
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=4CC55894.5040509@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