From: Benny Halevy <bhalevy@panasas.com>
To: "William A. (Andy) Adamson" <androsadamson@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/3] SQUASHME: pnfs-submit: filelayout: add nr_pages back to write_pagelist api
Date: Tue, 20 Jul 2010 17:07:07 +0300 [thread overview]
Message-ID: <4C45AD8B.3070802@panasas.com> (raw)
In-Reply-To: <AANLkTinv670aR9NSYb7O=KdJAhhsRHo3gZTcSrj0MHY_@mail.gmail.com>
On 2010-07-20 16:50, William A. (Andy) Adamson wrote:
> The file layout does not use nr_pages. The calculation is easy. No
True, but we should strive for a coherent interface IMO,
even if it's not the absolute minimal one.
> need to pass the extra parameter. Why not just call
> nfs_page_array_len() in the layout drivers that need it?
It's defined in fs/nfs/internal.h, so to use it officially
it should be moved to a public header file or exported as
a public function.
Benny
>
> -->Andy
>
> On Tue, Jul 20, 2010 at 1:57 AM, Benny Halevy <bhalevy@panasas.com> wrote:
>> Signed-off-by: Benny Halevy <bhalevy@panasas.com>
>> ---
>> fs/nfs/nfs4filelayout.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/fs/nfs/nfs4filelayout.c b/fs/nfs/nfs4filelayout.c
>> index 9b6ba8d..b2ce478 100644
>> --- a/fs/nfs/nfs4filelayout.c
>> +++ b/fs/nfs/nfs4filelayout.c
>> @@ -244,7 +244,7 @@ filelayout_read_pagelist(struct nfs_read_data *data, unsigned nr_pages)
>>
>> /* Perform async writes. */
>> static enum pnfs_try_status
>> -filelayout_write_pagelist(struct nfs_write_data *data, int sync)
>> +filelayout_write_pagelist(struct nfs_write_data *data, unsigned nr_pages, int sync)
>> {
>> struct pnfs_layout_segment *lseg = data->pdata.lseg;
>> struct nfs4_pnfs_ds *ds;
>> --
>> 1.7.1.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
--
Benny Halevy
Software Architect
Panasas, Inc.
bhalevy@panasas.com
Tel/Fax: +972-3-647-8340
Mobile: +972-54-802-8340
Panasas: The Leader in Parallel Storage
www.panasas.com
next prev parent reply other threads:[~2010-07-20 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 5:55 [PATCH 0/9] layout driver api cleanup and usage Benny Halevy
2010-07-20 5:57 ` [PATCH 1/3] SQUASHME: pnfs-submit: add nr_pages back to write_pagelist api Benny Halevy
2010-07-20 5:57 ` [PATCH 2/3] SQUASHME: pnfs-submit: filelayout: " Benny Halevy
2010-07-20 13:50 ` William A. (Andy) Adamson
2010-07-20 14:07 ` Benny Halevy [this message]
2010-07-20 14:09 ` Trond Myklebust
2010-07-20 5:57 ` [PATCH 3/3] SQUASHME: pnfs-submit: use nfs_page_array_len in pnfs_try_to_read_data Benny Halevy
2010-07-20 5:58 ` [PATCH 1/3] SQUASHME: pnfs-block: use new commit api Benny Halevy
2010-07-20 5:58 ` [PATCH 2/3] SQUASHME: pnfs-block: use new read_pagelist api Benny Halevy
2010-07-20 5:58 ` [PATCH 3/3] SQUASHME: pnfs-block: use new write_pagelist api Benny Halevy
2010-07-20 5:58 ` [PATCH 1/3] SQUASHME: pnfs-obj: use new commit api Benny Halevy
2010-07-20 5:58 ` [PATCH 2/3] SQAUSHME: pnfs-obj: use new read_pagelist api Benny Halevy
2010-07-20 5:58 ` [PATCH 3/3] SQUASHME: pnfs-obj: use new write_pagelist api Benny Halevy
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=4C45AD8B.3070802@panasas.com \
--to=bhalevy@panasas.com \
--cc=androsadamson@gmail.com \
--cc=linux-nfs@vger.kernel.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.