Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756650AbZCXJJl (ORCPT ); Tue, 24 Mar 2009 05:09:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753743AbZCXJJb (ORCPT ); Tue, 24 Mar 2009 05:09:31 -0400 Received: from gw-ca.panasas.com ([209.116.51.66]:5079 "EHLO laguna.int.panasas.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752300AbZCXJJa (ORCPT ); Tue, 24 Mar 2009 05:09:30 -0400 Message-ID: <49C8A2ED.2020203@panasas.com> Date: Tue, 24 Mar 2009 11:07:57 +0200 From: Boaz Harrosh User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Linus Torvalds , Andrew Morton CC: Jeff Garzik , linux-fsdevel , open-osd , Evgeniy Polyakov , James Bottomley , linux-kernel , FUJITA Tomonori Subject: Re: [PATCHSET 0/8 version 4] exofs for kernel 2.6.30 References: <49C1331D.1080805@panasas.com> In-Reply-To: <49C1331D.1080805@panasas.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Mar 2009 09:09:27.0146 (UTC) FILETIME=[3B7A04A0:01C9AC60] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3364 Lines: 82 Boaz Harrosh wrote: > What's new since last iteration: > > * I completely re-wrote the [PATCH 4/8] exofs: address_space_operations > in which we actually write/read to/from osd-storage. The difference is > that now we try to accumulate as many contiguous pages as possible and > send them as one large request. As opposed to writing each page at a > time, in the previous patchset. > > * [PATCH 5/8] exofs: dir_inode and directory operations received lots > of love thanks to Evgeniy Polyakov's grate comments. > > exofs is a file system that uses an OSD device as it's back store. > > OSD is a new T10 command set that views storage devices not as a large/flat > array of sectors but as a container of objects, each having a length, quota, > time attributes and more. Each object is addressed by a 64bit ID, and is > contained in a 64bit ID partition. Each object has associated attributes > attached to it, which are integral part of the object and provide metadata about > the object. The standard defines some common obligatory attributes, but user > attributes can be added as needed. > > Here is the list of patches > [PATCH 1/8] exofs: Kbuild, Headers and osd utils > [PATCH 2/8] exofs: file and file_inode operations > [PATCH 3/8] exofs: symlink_inode and fast_symlink_inode operations > [PATCH 4/8] exofs: address_space_operations > [PATCH 5/8] exofs: dir_inode and directory operations > [PATCH 6/8] exofs: super_operations and file_system_type > [PATCH 7/8] exofs: Documentation > [PATCH 8/8] fs: Add exofs to Kernel build > > This patchset is also available on: > git-clone git://git.open-osd.org/linux-open-osd.git linux-next > or on the web at: > http://git.open-osd.org/gitweb.cgi?p=linux-open-osd.git;a=shortlog;h=refs/heads/linux-next > > (Above tree is based on Linus v2.6.29-rc8-212-g8144737) > > If anyone wants to actually run this code and test it > then please start reading at: > http://open-osd.org > You will need to checkout the out-of-tree git (below) for the user-mode utilities. > Also the exofs.txt file in patch 7/8 should help > > If you want to review the user-mode library and supporting plumbings, > git-clone git://git.open-osd.org/open-osd.git > or on the web at: > http://git.open-osd.org/gitweb.cgi?p=open-osd.git;a=summary > > Boaz > Hi Linus In the matter of above new exofs file system. Andrew Morton has suggested that you might prefer to directly pull form the open-osd git-tree instead of him pushing it through his tree? The exofs tree will be pushed only at second stage of the merge window as it is dependent on patches to the osd-initiator which sit in James's scsi-misc tree. I'm monitoring the git-commits-head@vger.kernel.org mailing list and once I see all dependent patches are in main-line I'll send you a pull request, or Andrew which ever you prefer? Some background ml thread: http://www.spinics.net/lists/linux-scsi/msg32104.html The code was sitting in linux-next since 2.6.29-rc1. It is Kconfigured off by default and it will only impacted osd early adaptors/developers. Thank you very much in advance Boaz Harrosh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/