From: Eric Sandeen <sandeen@sandeen.net>
To: Barry Naujok <bnaujok@sgi.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: REVIEW: Enhance xfs_repair -P option to disable libxfs xfs_buf_t locking
Date: Thu, 29 May 2008 19:52:23 -0500 [thread overview]
Message-ID: <483F4FC7.3060801@sandeen.net> (raw)
In-Reply-To: <op.ubxy8gk63jf8g2@pc-bnaujok.melbourne.sgi.com>
Barry Naujok wrote:
> I hope the subject is explanation enough :)
not really ;)
Hum, if I normally lock why do I not want to lock? Locking good?
Locking bad? Locking too slow? locking for what? Incoherency ok? Man
page updates? :)
-Eric
next prev parent reply other threads:[~2008-05-30 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 0:49 REVIEW: Enhance xfs_repair -P option to disable libxfs xfs_buf_t locking Barry Naujok
2008-05-30 0:52 ` Eric Sandeen [this message]
2008-05-30 1:03 ` Barry Naujok
2008-05-30 1:13 ` Barry Naujok
2008-05-30 1:17 ` Eric Sandeen
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=483F4FC7.3060801@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bnaujok@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.