From patchwork Fri Aug 9 21:28:51 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: jon ernst X-Patchwork-Id: 266173 Return-Path: X-Original-To: patchwork-incoming@ozlabs.org Delivered-To: patchwork-incoming@ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id C3D3E2C0095 for ; Sat, 10 Aug 2013 07:28:56 +1000 (EST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031207Ab3HIV2z (ORCPT ); Fri, 9 Aug 2013 17:28:55 -0400 Received: from mout.gmx.net ([74.208.4.201]:56755 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031203Ab3HIV2z (ORCPT ); Fri, 9 Aug 2013 17:28:55 -0400 Received: from mailout-us.gmx.com ([172.19.198.46]) by mrigmx.server.lan (mrigmxus002) with ESMTP (Nemesis) id 0MDPx3-1VLvwJ0kph-00Gn98 for ; Fri, 09 Aug 2013 23:28:54 +0200 Received: (qmail 16013 invoked by uid 0); 9 Aug 2013 21:28:54 -0000 Received: from 198.180.159.2 by rms-us008 with HTTP Cc: linux-doc@vger.kernel.org Date: Fri, 09 Aug 2013 17:28:51 -0400 From: "jon ernst" Message-ID: <20130809212851.284520@gmx.com> MIME-Version: 1.0 Subject: [PATCH]ext4: Log inline_data feature in Documentation To: linux-ext4@vger.kernel.org X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: RDp3ckAO3zOlOKCRun0h+BB+IGRvb0DZ Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org When I tested inline_data feature, I found it hasn't been documented in ext4.txt. Signed-off-by:jon ernst --- -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/Documentation/filesystems/ext4.txt b/Documentation/filesystems/ext4.txt index f7cbf57..f2de1a1 100644 --- a/Documentation/filesystems/ext4.txt +++ b/Documentation/filesystems/ext4.txt @@ -99,6 +99,7 @@ Note: More extensive information for getting started with ext4 can be  * large block (up to pagesize) support  * efficient new ordered mode in JBD2 and ext4(avoid using buffer head to force    the ordering) +* allows small files or directories to be stored within the in-inode extended attribute area via inline_data    [1] Filesystems with a block size of 1k may see a limit imposed by the  directory hash tree having a maximum depth of two.