public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lachlan McIlroy <lachlan@sgi.com>
To: markgw@sgi.com
Cc: David Chinner <dgc@sgi.com>, Niv Sardi <xaiki@cxhome.ath.cx>,
	xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [RFC, patch 1/2] Allow up to 1GB logs in mkfs.xfs
Date: Mon, 25 Feb 2008 12:31:19 +1100	[thread overview]
Message-ID: <47C21A67.1010706@sgi.com> (raw)
In-Reply-To: <47C21585.8030504@sgi.com>

Mark Goodwin wrote:
> 
> David Chinner wrote:
>> On Fri, Feb 22, 2008 at 04:44:02PM +1100, Lachlan McIlroy wrote:
>>> David Chinner wrote:
>>>> On Fri, Feb 22, 2008 at 01:44:38PM +1100, Niv Sardi wrote:
>>>>> David Chinner <dgc@sgi.com> writes:
>>>>>> Increase the maximum log size supported by mkfs.
>>>> ....
>>>>>> Hence logs larger than 2^30 will not work without kernel
>>>>>> modifications.
>> Therefore this change is limited to increasing the
>>>>>> log size to what we can currently support in kernel space with
>>>>>> needing kernel modifications.
> 
> Does anyone know of any work in mainline to address this?
> 
>>>>> I'm glad you got time to get around this, I didn't include it in the
>>>>> first batch as I was told it 'broke things'.
>>>> Right. There's all sorts of nasties lurking if we go over 1GB in
>>>> size, but AFAICT up to 1GB is OK. There's still lots of validation
>>>> needing to be done - that's why this is an "RFC" and not something
>>>> ready for checkin yet. That's where more eye's and testers are
>>>> handy...
>>> Dave, have you run any tests to see if we get any speed-ups with
>>> this change?
>>
>> Not yet - I've been running it through QA with different log sizes
>> first to see if there's anything obviously broken with the kernel
>> w.r.t. larger log sizes (nothing wrong so far).
> 
> What sort of improvements are we expecting? Log bound benchmarks will
> tail-push later than they do now, wont they? Which particular benchmarks
> are you thinking of running?
> 

Does a larger on-disk log mean we can have a lot more items in the AIL?

  reply	other threads:[~2008-02-25  1:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 23:08 [RFC, patch 1/2] Allow up to 1GB logs in mkfs.xfs David Chinner
2008-02-22  2:44 ` Niv Sardi
2008-02-22  5:03   ` David Chinner
2008-02-22  5:44     ` Lachlan McIlroy
2008-02-22  6:53       ` David Chinner
2008-02-25  1:10         ` Mark Goodwin
2008-02-25  1:31           ` Lachlan McIlroy [this message]
2008-02-28 18:17             ` David Chinner

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=47C21A67.1010706@sgi.com \
    --to=lachlan@sgi.com \
    --cc=dgc@sgi.com \
    --cc=markgw@sgi.com \
    --cc=xaiki@cxhome.ath.cx \
    --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