From: Jeff Blaine <jblaine-GbE5gUWZ6k7k1uMJSBkQmQ@public.gmane.org>
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@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, 05 Feb 2013 15:02:52 -0500 [thread overview]
Message-ID: <5111656C.90109@kickflop.net> (raw)
In-Reply-To: <20130205142307.58d87a21-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
>> 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.
I opened one an hour or so ago, so that's done.
Should I test with Fedora 17 or Fedora 18 for the sake of this?
Just because 18 is newer doesn't mean it's the most appropriate
for this test need, eh?
next prev parent reply other threads:[~2013-02-05 20:02 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
[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 [this message]
[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=5111656C.90109@kickflop.net \
--to=jblaine-gbe5guwz6k7k1umjsbkqmq@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.