Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Jeff Blaine <jblaine-GbE5gUWZ6k7k1uMJSBkQmQ@public.gmane.org>
Cc: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: Read speed
Date: Tue, 5 Feb 2013 14:20:58 -0500	[thread overview]
Message-ID: <20130205142058.7618dfcf@corrin.poochiereds.net> (raw)
In-Reply-To: <51113D76.80609-GbE5gUWZ6k7k1uMJSBkQmQ@public.gmane.org>

On Tue, 05 Feb 2013 12:12:22 -0500
Jeff Blaine <jblaine-GbE5gUWZ6k7k1uMJSBkQmQ@public.gmane.org> wrote:

> Thank you for the thorough reply, Steve. It's nice to
> read of the progress in 2012, but RHEL 6.3 and what is
> supported there is what we have to work with. It is the
> latest supported version, as you surely know, so it
> seems like we'll have to wait quite awhile before
> getting the module's read performance increases.
> 
> We're dealing with 9 US sites, nightly time window (which
> we're exceeding) for transferring large amounts of data
> over 1.5Mbps links).
> 
> Back to the drawing board.
> 
> Thanks again.
> 

I think you're basically out of luck for now...

Long haul links are really a pessimal case for the older code that did
synchronous reads and writes. You spend most of your time waiting
around for the calls to go back and forth.

I believe Sachin is looking at backporting the async read patches for
6.5. The async write code is already in 6.3 (I think). You should
definitely open a support case since documented customer demand helps
us make the case for including these sorts of changes in an update.

-- 
Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

  parent reply	other threads:[~2013-02-05 19:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05  1:23 Read speed Jeff Blaine
2013-02-05  2:03 ` Steve French
     [not found]   ` <CAH2r5mvbbuo9e30kuRFp9eegJqq_9HLR9=oaGvFqyMi-aBKXTQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-05 17:12     ` Jeff Blaine
     [not found]       ` <51113D76.80609-GbE5gUWZ6k7k1uMJSBkQmQ@public.gmane.org>
2013-02-05 19:20         ` Jeff Layton [this message]
     [not found]           ` <20130205142058.7618dfcf-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2013-02-05 19:23             ` Jeff Layton
     [not found]               ` <20130205142307.58d87a21-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2013-02-05 20:02                 ` Jeff Blaine
     [not found]                   ` <5111656C.90109-GbE5gUWZ6k7k1uMJSBkQmQ@public.gmane.org>
2013-02-05 20:17                     ` Jeff Layton
2013-03-11 17:54                     ` Jeff Blaine
     [not found]                       ` <513E1A3E.1080404-GbE5gUWZ6k7k1uMJSBkQmQ@public.gmane.org>
2013-03-11 17:57                         ` 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=20130205142058.7618dfcf@corrin.poochiereds.net \
    --to=jlayton-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=jblaine-GbE5gUWZ6k7k1uMJSBkQmQ@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=sprabhu-H+wXaHxf7aLQT0dZR+AlfA@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