From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756628AbZBPJ2B (ORCPT ); Mon, 16 Feb 2009 04:28:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756123AbZBPJ1s (ORCPT ); Mon, 16 Feb 2009 04:27:48 -0500 Received: from srv5.dvmed.net ([207.36.208.214]:48774 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752691AbZBPJ1q (ORCPT ); Mon, 16 Feb 2009 04:27:46 -0500 Message-ID: <49993182.3010707@garzik.org> Date: Mon, 16 Feb 2009 04:27:30 -0500 From: Jeff Garzik User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Boaz Harrosh CC: FUJITA Tomonori , avishay@gmail.com, akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org, osd-dev@open-osd.org, linux-kernel@vger.kernel.org, James.Bottomley@HansenPartnership.com, jens.axboe@oracle.com, linux-scsi@vger.kernel.org Subject: Re: [PATCH 1/8] exofs: Kbuild, Headers and osd utils References: <1234185129-31858-1-git-send-email-bharrosh@panasas.com> <20090216131806X.fujita.tomonori@lab.ntt.co.jp> <499928A3.60507@panasas.com> <20090216180028C.fujita.tomonori@lab.ntt.co.jp> <49992F99.1060404@panasas.com> In-Reply-To: <49992F99.1060404@panasas.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) X-Spam-Report: SpamAssassin version 3.2.5 on srv5.dvmed.net summary: Content analysis details: (-4.4 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Boaz Harrosh wrote: > FUJITA Tomonori wrote: >> Boaz Harrosh wrote: >>> Also looking >>> ahead I will have RAID 0, 1, 5, and 6 on objects of different devices. bio >>> is the perfect collector for memory information in this situation. >> You will add such features to exofs, handling multiple devices >> internally? > Multiple objects on Multiple devices, Yes. That sort of feature does not belong in exofs, but somewhat separate. Ideally we should be able to share "MD for OSD" with other OSD filesystems, and the "osdblk" device that I will produce once libosd hits upstream. Jeff