mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jan Weitzel <j.weitzel@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC] ramfs: rember last accessed chunk
Date: Tue, 15 May 2012 21:29:34 +0200	[thread overview]
Message-ID: <20120515192934.GM30400@pengutronix.de> (raw)
In-Reply-To: <1337073346-4256-1-git-send-email-j.weitzel@phytec.de>

Hi Jan,

On Tue, May 15, 2012 at 11:15:46AM +0200, Jan Weitzel wrote:
> Writing big files takes longer and longer because of the chunk list
> By storing a pointer of the recent used chunk in the inode, access times are
> improved.
> Testet on with tftp 10M:
> OMAP4 chunk size 4096: 12244ms 8192: 4239ms
> 	patched        2647ms        2785ms
> i.MX35 chunk size 8192: 7225ms
> 	patched		2691ms
> 

The numbers look good and the code looks sane. We can give it a try. Two
nitpicks below.

> No impact on much smaller files seen
> 
> Signed-off-by: Jan Weitzel <j.weitzel@phytec.de>
> ---
>  fs/ramfs.c |   46 ++++++++++++++++++++++++++++++++++++----------
>  1 files changed, 36 insertions(+), 10 deletions(-)
> 
> diff --git a/fs/ramfs.c b/fs/ramfs.c
> index 83ab6df..5c7410b 100644
> --- a/fs/ramfs.c
> +++ b/fs/ramfs.c
> @@ -48,6 +48,10 @@ struct ramfs_inode {
>  
>  	ulong size;
>  	struct ramfs_chunk *data;
> +	

Trailing whitespace here.

> +	/* Points to recently used chunk */
> +	int recent_chunk;
> +	struct ramfs_chunk *recent_chunkp;
>  };
>  
>  struct ramfs_priv {
> @@ -297,6 +301,34 @@ static int ramfs_close(struct device_d *dev, FILE *f)
>  	return 0;
>  }
>  
> +static struct ramfs_chunk *ramfs_find_chunk(struct ramfs_inode *node, int chunk)
> +{
> +	struct ramfs_chunk *data;
> +	int left = chunk;
> +
> +	if (chunk == 0)
> +		return node->data;
> +
> +	if (node->recent_chunk == chunk)
> +		return node->recent_chunkp;
> +
> +	if (node->recent_chunk < chunk && node->recent_chunk != 0) {
> +		/* Start at last known chunk */
> +		data = node->recent_chunkp;
> +		left -= node->recent_chunk;
> +	} else
> +		/* Start at first chunk */
> +		data = node->data;

if you have brackets in the if path you should add them in the else path
aswell.

>  		}
> +		if (node->recent_chunk > newchunks) 

Also trailing whitespace

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-05-15 19:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15  9:15 Jan Weitzel
2012-05-15 19:29 ` Sascha Hauer [this message]
2012-05-16  6:10   ` [PATCH] " Jan Weitzel
2012-05-16 11:20     ` Sascha Hauer
2012-05-16 18:42       ` Uwe Kleine-König

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=20120515192934.GM30400@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=j.weitzel@phytec.de \
    /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