From: Zach Brown <zab@zabbo.net>
To: Sage Weil <sage@newdream.net>
Cc: Noah Watkins <noah@noahdesu.com>, ceph-devel@lists.sourceforge.net
Subject: Re: [RFC] separate otw data from host data
Date: Fri, 06 Nov 2009 09:47:35 -0800 [thread overview]
Message-ID: <4AF46137.2050604@zabbo.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0911052224121.24285@cobra.newdream.net>
> My biggest concern with all of this is really just that the type names
> don't clearly indicate which ones are OTW and which aren't. The most
> helpful cleanup may just be to include _otw_ or something similar in the
> ceph_fs/msgr/rados headers. (Though it's really on-disk and/or
> over-the-wire.)
In the past I've used _disk or _wire suffixes in various projects. It
works out pretty well, I think.
- z
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
next prev parent reply other threads:[~2009-11-06 17:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 2:03 [RFC] separate otw data from host data Noah Watkins
2009-11-06 5:33 ` Sage Weil
2009-11-06 6:09 ` Noah Watkins
2009-11-06 6:37 ` Sage Weil
2009-11-06 7:31 ` Noah Watkins
2009-11-06 17:47 ` Zach Brown [this message]
2009-11-06 19:29 ` [RFC] v2 " Noah Watkins
2009-11-06 19:44 ` Sage Weil
2009-11-06 20:04 ` Noah Watkins
2009-11-06 20:08 ` Yehuda Sadeh Weinraub
2009-11-06 20:19 ` Noah Watkins
2009-11-06 20:49 ` Sage Weil
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=4AF46137.2050604@zabbo.net \
--to=zab@zabbo.net \
--cc=ceph-devel@lists.sourceforge.net \
--cc=noah@noahdesu.com \
--cc=sage@newdream.net \
/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.