| To: | Cosmo Nova <cs_mcc98@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: file system defragmentation |
| From: | David Chinner <dgc@xxxxxxx> |
| Date: | Wed, 9 Aug 2006 09:34:25 +1000 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <5408752.post@talk.nabble.com> |
| References: | <4f52331f050826001612f8e323@mail.gmail.com> <20050826101131.GA24544@ii.uib.no> <4f52331f0508260848782f240a@mail.gmail.com> <E4E12CD035E14A4AB8C36E0F4B7143F7277DED@iu-mssg-mbx09.exchange.iu.edu> <43112C5D.8090202@sgi.com> <20050828034108.73921.qmail@web34103.mail.mud.yahoo.com> <5408752.post@talk.nabble.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.1i |
On Wed, Jul 19, 2006 at 09:23:42PM -0700, Cosmo Nova wrote: > > what is the maximum tolerance for the delayed allocations pls? I guess it's > not possible to buf a GB size file and delay its allocation? Sure it is. The limit on how much is buffered before writeback (and therefore allocation) is determined by how much memory you have and your /proc/sys/vm/dirty* tunable settings. This can range from a few MB to a few TB of data depending on how big your machine is ;) Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software Group |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] kill iop_abort item_op, Nathan Scott |
|---|---|
| Next by Date: | Re: [PATCH 1/2] Add new spin_lock for i_flags of xfs_inode, Nathan Scott |
| Previous by Thread: | [PATCH 1/2] Add new spin_lock for i_flags of xfs_inode, Masayuki Saito |
| Next by Thread: | Re: [PATCH] kill no-op buf macros, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |