From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: Improve scalability of busy extent tracking
Date: Thu, 22 Apr 2010 13:08:49 -0400 [thread overview]
Message-ID: <20100422170848.GA26101@infradead.org> (raw)
In-Reply-To: <20100422161626.GE23541@dastard>
Been looking at this a bit and I have a theory:
- a tid is not actually unique to a xfs_trans structure, if
we call xfs_trans_dup a single xlog_ticket, and with that the
tid is re-used by multiple transaction structure.
- because of that the major semantic change in the version vs
the previous one is that we now do not force the synchronous
transaction for the case where we re-used a block in
the rolled over transaction.
Still not quite sure about the implications of this.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-22 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 5:47 [PATCH] xfs: Improve scalability of busy extent tracking Dave Chinner
2010-04-22 11:01 ` Christoph Hellwig
2010-04-22 16:16 ` Dave Chinner
2010-04-22 17:08 ` Christoph Hellwig [this message]
2010-04-23 3:24 ` Dave Chinner
2010-04-22 11:07 ` Christoph Hellwig
2010-04-22 17:10 ` Christoph Hellwig
2010-04-23 3:25 ` Dave 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=20100422170848.GA26101@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.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