mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Jeff Layton <jlayton@samba.org>
Cc: Steve French <smfrench@gmail.com>,
	"J. R. Okajima" <hooanon05@yahoo.co.jp>,
	Jesper Juhl <jj@chaosbits.net>,
	linux-kernel@vger.kernel.org, Alan Piszcz <ap@solarrain.com>,
	Steve French <sfrench@samba.org>,
	linux-cifs@vger.kernel.org
Subject: Re: Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2
Date: Fri, 26 Aug 2011 18:57:29 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1108261844170.2203@p34.internal.lan> (raw)
In-Reply-To: <20110826175940.2830044d@tlielax.poochiereds.net>



On Fri, 26 Aug 2011, Jeff Layton wrote:

> On Thu, 18 Aug 2011 14:52:57 -0400
> Jeff Layton <jlayton@samba.org> wrote:
>
>> On Thu, 18 Aug 2011 14:18:15 -0400 (EDT)
>> Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>>
>>>
>> Like I said, read performance with cifs.ko just plain sucks currently.
>>
>> Don't look for cifs.ko to achieve anywhere near NFS' performance unless
>> you jump through some very odd hoops (like multithreading your workload
>> in userspace, etc). cifs.ko just doesn't do a good job of keeping the
>> pipe "stuffed" as most calls are handled synchronously. A single task
>> can only handle one call on the wire in most cases. The exception here
>> is writes, but that just recently changed...
>>
>> Reads are done using relatively small buffers and then copied to
>> pagecache. Part of what I'm working on will be to allow for much larger
>> reads directly into the pagecache. That should also help performance
>> significantly.
>>
>
> I just posted a patchset that should improve the performance of
> buffered reads. It's rather large but should apply to current upstream
> kernels. If you've had problems with cifs.ko read performance in the
> past, then this would be a good time to step up and help test them.
>
> If it makes things easier, then the patchset is also available via the
> cifs-3.2 branch of my public git tree:
>
>    http://git.kernel.org/?p=linux/kernel/git/jlayton/linux.git;a=shortlog;h=refs/heads/cifs-3.2
>
> Thanks,
> -- 
> Jeff Layton <jlayton@samba.org>

Hi Jeff,

This was working earlier..

# mount -t cifs //10.0.1.1/x /mnt -o user=XXXXXXX,pass=XXXXXXXX
mount error(12): Cannot allocate memory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

I'll need to contact the owner of the host to see if something has changed as 
this _was_ working previously.

Justin.

>

  reply	other threads:[~2011-08-26 22:57 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15  9:10 Kernel 3.0: Instant kernel crash when mounting CIFS Justin Piszcz
2011-08-15  9:18 ` Jesper Juhl
2011-08-15 10:47   ` Jeff Layton
2011-08-15 10:54     ` Justin Piszcz
2011-08-15 18:01       ` Justin Piszcz
2011-08-15 18:09         ` Steve French
2011-08-15 19:31         ` Dave Jones
2011-08-17 19:16         ` Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2 Justin Piszcz
     [not found]           ` <alpine.DEB.2.02.1108171545190.5877@p34.internal.lan>
2011-08-17 19:47             ` Justin Piszcz
2011-08-17 20:13               ` Jeff Layton
2011-08-17 20:45                 ` Justin Piszcz
2011-08-17 21:11                   ` Arnaud Lacombe
2011-08-17 21:53                     ` Justin Piszcz
2011-08-17 22:13                       ` Justin Piszcz
2011-08-17 22:18                         ` Justin Piszcz
2011-08-17 23:31           ` Valdis.Kletnieks
2011-08-18  3:19           ` J. R. Okajima
2011-08-18 10:35             ` Justin Piszcz
2011-08-18 12:14               ` Justin Piszcz
2011-08-18 12:22                 ` Justin Piszcz
2011-08-18 13:11                   ` Jeff Layton
2011-08-18 13:15                     ` Justin Piszcz
2011-08-18 17:04                       ` Jeff Layton
2011-08-18 17:15                         ` Steve French
2011-08-18 17:16                         ` Justin Piszcz
2011-08-18 17:25                           ` Steve French
2011-08-18 17:33                             ` Justin Piszcz
2011-08-18 17:43                               ` Steve French
2011-08-18 18:18                                 ` Justin Piszcz
2011-08-18 18:52                                   ` Jeff Layton
2011-08-18 18:54                                     ` Justin Piszcz
2011-08-18 19:02                                       ` Steve French
2011-08-26 21:59                                     ` Jeff Layton
2011-08-26 22:57                                       ` Justin Piszcz [this message]
2011-08-26 23:05                                         ` Steve French
2011-08-26 23:16                                           ` Justin Piszcz
2011-08-27 14:31                                             ` Jeff Layton
2011-08-18 17:36                             ` Kong Li
2011-08-18 18:33                             ` Jeff Layton
2011-08-18 14:19                 ` J. R. Okajima
2011-08-18 16:01                 ` Steve French
2011-08-18 16:02                   ` 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=alpine.DEB.2.02.1108261844170.2203@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=ap@solarrain.com \
    --cc=hooanon05@yahoo.co.jp \
    --cc=jj@chaosbits.net \
    --cc=jlayton@samba.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfrench@samba.org \
    --cc=smfrench@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®