From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zach Brown Subject: Re: [RFC] separate otw data from host data Date: Fri, 06 Nov 2009 09:47:35 -0800 Message-ID: <4AF46137.2050604@zabbo.net> References: <3A19C8FD-BDC5-41A5-BBED-8C8CE47FBEFC@soe.ucsc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ceph-devel-bounces@lists.sourceforge.net To: Sage Weil Cc: Noah Watkins , ceph-devel@lists.sourceforge.net List-Id: ceph-devel.vger.kernel.org > 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