From: Sunil Mushran <Sunil.Mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] dentry locks
Date: Wed, 16 Apr 2008 12:42:31 -0700 [thread overview]
Message-ID: <480656A7.8030201@oracle.com> (raw)
In-Reply-To: <20080416191617.GD31299@wotan.suse.de>
Mark Fasheh wrote:
> Yeah, it breaks the protocol ;)
I meant, other than that. As in, we can always queue up this change
the next time we break the protocol for a better reason.
> What do the tcp dumps look like? Is it raw binary data, is the binary
> converted into hex, etc?
dentry lock from debugfs: N0000000000000005000d6a02
raw tcpdump: 4e303030303030303030303030303030350000000000000d6a02
N 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 00 0d6a02
4e303030303030303030303030303030350000000000000d6a02
As all other locknames are strings, if I need to wade thru tcpdumps,
I simply grep. If not for that, one can easily spend a day just searching
for the appropriate packets. So this is not a useless exercise.
prev parent reply other threads:[~2008-04-16 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 1:54 [Ocfs2-devel] dentry locks Sunil Mushran
2008-04-16 18:20 ` Mark Fasheh
2008-04-16 18:29 ` Sunil Mushran
2008-04-16 19:03 ` Mark Fasheh
2008-04-16 19:10 ` Sunil Mushran
2008-04-16 19:16 ` Mark Fasheh
2008-04-16 19:42 ` Sunil Mushran [this message]
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=480656A7.8030201@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.oracle.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;
as well as URLs for NNTP newsgroup(s).