public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Andi Kleen <andi@firstfloor.org>
Cc: David Chinner <dgc@sgi.com>, xfs-dev <xfs-dev@sgi.com>,
	xfs-oss <xfs@oss.sgi.com>
Subject: Re: Review: Concurrent Multi-File Data Streams
Date: Sat, 12 May 2007 22:08:56 -0500	[thread overview]
Message-ID: <46468148.7000708@sandeen.net> (raw)
In-Reply-To: <p73sla1ev7o.fsf@bingen.suse.de>

Andi Kleen wrote:

> Also centisecs is a really ugly unit whose use should be probably not propagated.
> 
> -Andi

Hmm at one point I thought the preferred unit for this sort of tuneable 
*was* centisecs.  What's the unit du jour?

[root@neon ~]# sysctl -a  |grep cent
vm.dirty_expire_centisecs = 2999
vm.dirty_writeback_centisecs = 499
fs.xfs.age_buffer_centisecs = 1500
fs.xfs.xfsbufd_centisecs = 100
fs.xfs.xfssyncd_centisecs = 3000

I think xfs was following the vm lead at one point.

-Eric

  reply	other threads:[~2007-05-13  3:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11  0:36 Review: Concurrent Multi-File Data Streams David Chinner
2007-05-12 18:46 ` Andi Kleen
2007-05-13  3:08   ` Eric Sandeen [this message]
2007-05-14  5:35     ` Review: Concurrent Multi-File Data Streams - centisecs Timothy Shimmin
     [not found]   ` <000001c79544$44076ac0$0501010a@DCHATTERTONLAPTOP>
2007-05-14 22:39     ` Review: Concurrent Multi-File Data Streams Andi Kleen
2007-05-15  0:05       ` David Chinner
2007-05-15  0:15       ` David Chatterton
2007-05-13 20:59 ` Christoph Hellwig
2007-05-15  6:23   ` David Chinner
2007-05-15  9:23     ` Christoph Hellwig
2007-09-20  1:31 ` Hxsrmeng
2007-09-21  9:13   ` Leon Kolchinsky
2007-09-21 12:55     ` David Chinner
     [not found]       ` <1190399077.3795.86.camel@localhost.localdomain>
2007-09-23  7:45         ` David Chinner
2007-09-23 15:47           ` Ming Zhang

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=46468148.7000708@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=andi@firstfloor.org \
    --cc=dgc@sgi.com \
    --cc=xfs-dev@sgi.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