From: Christoph Hellwig <hch@infradead.org>
To: Olaf Weber <olaf@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@redhat.com>,
linux-mm@kvack.org, "MASON, CHRISTOPHER" <CHRIS.MASON@oracle.com>,
xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH] bump up nr_to_write in xfs_vm_writepage
Date: Tue, 7 Jul 2009 10:46:01 -0400 [thread overview]
Message-ID: <20090707144601.GA705@infradead.org> (raw)
In-Reply-To: <bzy8wj0bu72.fsf@fransum.emea.sgi.com>
On Tue, Jul 07, 2009 at 01:37:05PM +0200, Olaf Weber wrote:
> > In theory it should. But given the amazing feedback of the VM people
> > on this I'd rather make sure we do get the full HW bandwith on large
> > arrays instead of sucking badly and not just wait forever.
>
> So how do you feel about making the fudge factor tunable? I don't
> have a good sense myself of what the value should be, whether the
> hard-coded 4 is good enough in general.
A tunable means exposing an ABI, which I'd rather not do for a hack like
this. If you don't like the number feel free to experiment around with
it, SGI should have enough large systems that can be used to test this
out.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-07-07 14:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 21:29 Eric Sandeen
2009-07-07 9:07 ` Olaf Weber
2009-07-07 10:19 ` Christoph Hellwig
2009-07-07 10:33 ` KOSAKI Motohiro
2009-07-07 10:44 ` Christoph Hellwig
2009-07-09 2:04 ` KOSAKI Motohiro
2009-07-09 13:01 ` Chris Mason
2009-07-10 7:12 ` KOSAKI Motohiro
2009-07-24 5:20 ` Felix Blyakher
2009-07-24 5:33 ` KOSAKI Motohiro
2009-07-24 12:05 ` Chris Mason
2009-07-07 11:37 ` Olaf Weber
2009-07-07 14:46 ` Christoph Hellwig [this message]
2009-07-07 15:17 ` Chris Mason
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=20090707144601.GA705@infradead.org \
--to=hch@infradead.org \
--cc=CHRIS.MASON@oracle.com \
--cc=linux-mm@kvack.org \
--cc=olaf@sgi.com \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.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