From: Jim Rees <rees@umich.edu>
To: Peng Tao <bergwolf@gmail.com>
Cc: Trond.Myklebust@netapp.com, linux-nfs@vger.kernel.org,
bhalevy@tonian.com, Peng Tao <peng_tao@emc.com>
Subject: Re: [PATCH-RESEND 4/4] pnfsblock: do not ask for layout in pg_init
Date: Tue, 29 Nov 2011 12:48:30 -0500 [thread overview]
Message-ID: <20111129174830.GA3001@umich.edu> (raw)
In-Reply-To: <1322888194-3039-1-git-send-email-bergwolf@gmail.com>
Peng Tao wrote:
Asking for layout in pg_init will always make client ask for only 4KB
layout in every layoutget. This way, client drops the IO size information
that is meaningful for MDS in handing out layout.
In stead, if layout is not find in cache, do not send layoutget
at once. Wait until before issuing IO in pnfs_do_multiple_reads/writes
because that is where we know the real size of current IO. By telling the
real IO size to MDS, MDS will have a better chance to give proper layout.
Signed-off-by: Peng Tao <peng_tao@emc.com>
---
Resend to fix patch title. Sorry for the noise...
You may want to fix the patch date too, on this series and the other series
you sent earlier (later?). I know China is in a later timezone but I don't
think it's that much later.
next prev parent reply other threads:[~2011-11-29 17:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 4:56 [PATCH-RESEND 4/4] pnfsblock: do not ask for layout in pg_init Peng Tao
2011-11-29 17:48 ` Jim Rees [this message]
2011-11-30 5:43 ` tao.peng
2011-11-30 12:57 ` Benny Halevy
2011-11-30 13:17 ` Peng Tao
2011-12-01 1:18 ` Boaz Harrosh
2011-12-01 5:05 ` tao.peng
2011-12-01 9:57 ` Benny Halevy
2011-12-01 17:33 ` Boaz Harrosh
2011-12-01 18:00 ` Boaz Harrosh
2011-12-02 4:59 ` tao.peng
2011-12-07 14:08 ` Boaz Harrosh
2011-12-08 3:32 ` tao.peng
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=20111129174830.GA3001@umich.edu \
--to=rees@umich.edu \
--cc=Trond.Myklebust@netapp.com \
--cc=bergwolf@gmail.com \
--cc=bhalevy@tonian.com \
--cc=linux-nfs@vger.kernel.org \
--cc=peng_tao@emc.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;
as well as URLs for NNTP newsgroup(s).