mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Szabolcs Szakacsits <szaka@ntfs-3g.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	ywang221@hotmail.com
Subject: Re: [2.6.26 patch] fuse: fix thinko in max I/O size calucation
Date: Tue, 17 Jun 2008 19:59:15 +0300 (EEST)	[thread overview]
Message-ID: <Pine.LNX.4.62.0806171950350.23306@tamago.serverit.net> (raw)
In-Reply-To: <E1K8dgi-0005sl-El@pomaz-ex.szeredi.hu>


On Tue, 17 Jun 2008, Miklos Szeredi wrote:

> From: Miklos Szeredi <mszeredi@suse.cz>
> 
> Use max not min to enforce a lower limit on the max I/O size.

Big write is ok now, thanks. NTFS-3G in-memory write performance seems to 
be 6x better on a T9300 and quick tests seem to show that it's at least as 
fast as ext3 in-memory writes (but this needs more testing, etc).

However the max write size seems to be limited to 128kB. Is this 
intentional? If yes then

Acked-by: Szabolcs Szakacsits <szaka@ntfs-3g.org>

	Szaka

> This bug was introduced by
> 
>    commit e5d9a0df07484d6d191756878c974e4307fb24ce
>    Author: Miklos Szeredi <mszeredi@suse.cz>
>    Date:   Wed Apr 30 00:54:44 2008 -0700
>    
>        fuse: fix max i/o size calculation
> 
> Thanks to Brian Wang for noticing.
> 
> Reported-by: Brian Wang <ywang221@hotmail.com>
> CC: Szabolcs Szakacsits <szaka@ntfs-3g.org>
> Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
> ---
>  fs/fuse/inode.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> Index: linux-2.6/fs/fuse/inode.c
> ===================================================================
> --- linux-2.6.orig/fs/fuse/inode.c	2008-06-17 17:55:38.000000000 +0200
> +++ linux-2.6/fs/fuse/inode.c	2008-06-17 17:55:48.000000000 +0200
> @@ -591,7 +591,7 @@ static void process_init_reply(struct fu
>  		fc->bdi.ra_pages = min(fc->bdi.ra_pages, ra_pages);
>  		fc->minor = arg->minor;
>  		fc->max_write = arg->minor < 5 ? 4096 : arg->max_write;
> -		fc->max_write = min_t(unsigned, 4096, fc->max_write);
> +		fc->max_write = max_t(unsigned, 4096, fc->max_write);
>  		fc->conn_init = 1;
>  	}
>  	fuse_put_request(fc, req);
> @@ -667,7 +667,7 @@ static int fuse_fill_super(struct super_
>  	fc->flags = d.flags;
>  	fc->user_id = d.user_id;
>  	fc->group_id = d.group_id;
> -	fc->max_read = min_t(unsigned, 4096, d.max_read);
> +	fc->max_read = max_t(unsigned, 4096, d.max_read);
>  
>  	/* Used by get_root_inode() */
>  	sb->s_fs_info = fc;
> 

--
NTFS-3G:  http://ntfs-3g.org


  reply	other threads:[~2008-06-17 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17 16:05 Miklos Szeredi
2008-06-17 16:59 ` Szabolcs Szakacsits [this message]
2008-06-17 17:02   ` Miklos Szeredi

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=Pine.LNX.4.62.0806171950350.23306@tamago.serverit.net \
    --to=szaka@ntfs-3g.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@linux-foundation.org \
    --cc=ywang221@hotmail.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

all inboxes | Powered by JetHome®