Linux NFS development
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@tonian.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: NFS list <linux-nfs@vger.kernel.org>,
	Andy Adamson <andros@netapp.com>, Benny Halevy <benny@tonian.com>
Subject: Re: [RFC] pnfs: Add per-LD-info to nfs_pageio_descriptor
Date: Wed, 31 Aug 2011 14:27:17 -0700	[thread overview]
Message-ID: <4E5EA735.9020106@tonian.com> (raw)
In-Reply-To: <4E5C5785.4090607@panasas.com>

On 2011-08-29 20:22, Boaz Harrosh wrote:
> 
> What do you guys think? would it be acceptable to add a per-layout
> private-data to nfs_pageio_descriptor?
> 
> In obj-LD we have bunch of constrains on the size of the IO that
> involves some 64bit divisions, and math. These calculations are only
> needed to be preformed once when the offset of the first page is
> known. Then a simple wb_bytes can cache the results for subsequent
> calls. (And cannot be calculated before we know the IO's offset)
> 
> Also I might want to allocate the io_state earlier at the insert
> of the first page instead of at the actual call to write/read_pagelist,
> again, for the same reason above.
> 
> Today we get by because at the very end, if some constraints hit
> and not the full IO was preformed then we only set r/wdata->res.count
> to less then what was requested and these pages that are outside of
> the IOed range get to be read/written as part of a future request. But
> this is sub-optimal because that is done only at read/write_done time.
> By then the contiguous pages were already submitted to requests and
> the few left-over pages get submitted as their own request. This causes
> a seeky, unaligned and additional small IOs which, if calculated for at
> coalesce time, would be spared. With the up coming raid5/6 code this
> can cost dearly. (A single simple large contiguous IO becomes bunch of
> read-modify-write IOs)
> 
> I can see that also at filelayout_pg_test there are two 64bit divisions
> preformed on every page insert which could be optimized to a simple
> compare.
> 
> [BTW: Perhaps change the .write/read_pagelist() API to directly receive
>  the nfs_pageio_descriptor and avoid all the duplication of types and
>  members copy
> ]
> 
> I'm making pg_ld_private as a "long" because a long is good for a pointer
> as well as an integer.

I really prefer it to be a void * rather than long for the same reason
just as used in practically every other place.

Benny

> 
> Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
> 
> ---
> diff --git a/include/linux/nfs_page.h b/include/linux/nfs_page.h
> index e2791a2..c86bae5 100644
> --- a/include/linux/nfs_page.h
> +++ b/include/linux/nfs_page.h
> @@ -77,6 +77,7 @@ struct nfs_pageio_descriptor {
>  	int			pg_error;
>  	const struct rpc_call_ops *pg_rpc_callops;
>  	struct pnfs_layout_segment *pg_lseg;
> +	long pg_ld_private;
>  };
>  
>  #define NFS_WBACK_BUSY(req)	(test_bit(PG_BUSY,&(req)->wb_flags))
> --
> 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

      reply	other threads:[~2011-08-31 21:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30  3:22 [RFC] pnfs: Add per-LD-info to nfs_pageio_descriptor Boaz Harrosh
2011-08-31 21:27 ` Benny Halevy [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=4E5EA735.9020106@tonian.com \
    --to=bhalevy@tonian.com \
    --cc=andros@netapp.com \
    --cc=benny@tonian.com \
    --cc=bharrosh@panasas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox