Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
To: JM <johnmiller-06ZeP6ie+xM@public.gmane.org>
Cc: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Backported cifs module
Date: Wed, 08 Jun 2011 19:07:34 +0530	[thread overview]
Message-ID: <4DEF7B1E.7060008@suse.de> (raw)
In-Reply-To: <20110608085143.729e9c92-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>

On 06/08/2011 06:21 PM, Jeff Layton wrote:
> On Tue, 7 Jun 2011 23:46:02 +0200
> JM <johnmiller-06ZeP6ie+xM@public.gmane.org> wrote:
> 
>> Hi, 
>> sorry to disturb you directly, Steve French told me that you have
>> backported the cifs module to older kernels.
>> According to him, the latest release should fix some reading
>> slowness that I have experienced.
>> I am available if you need some testers too. 
>>
>> JM
>>
>> PS: I am using
>> opensuse with their 2.6.37.6 kernel.

Have you create a bug report against openSUSE-11.4 (I guess)? If yes,
could please add me in Cc? If not, can you create a bug report and
include me in Cc, I'll take a look at it.

Thanks,

> (cc'ing Steve and linux-cifs ml...)
> 
> The only commit I know of that would affect read performance is
> 2b6c26a0. A quick look at 2.6.37.y tree shows that it doesn't have that
> patch.
> 


-- 
Suresh Jayaraman

      parent reply	other threads:[~2011-06-08 13:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201106072346.02460.johnmiller@email.it>
     [not found] ` <201106072346.02460.johnmiller-06ZeP6ie+xM@public.gmane.org>
2011-06-08 12:51   ` Backported cifs module Jeff Layton
     [not found]     ` <20110608085143.729e9c92-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2011-06-08 13:37       ` Suresh Jayaraman [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=4DEF7B1E.7060008@suse.de \
    --to=sjayaraman-l3a5bk7wagm@public.gmane.org \
    --cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=johnmiller-06ZeP6ie+xM@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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