[18/22] orangefs: implement writepages

Message ID	20190418184113.9152-19-hubcap@kernel.org (mailing list archive)
State	New, archived
Headers	show Return-Path: <linux-fsdevel-owner@kernel.org> From: hubcap@kernel.org To: linux-fsdevel@vger.kernel.org, christoph@lameter.com Cc: Martin Brandenburg <martin@omnibond.com>, Mike Marshall <hubcap@omnibond.com> Subject: [PATCH 18/22] orangefs: implement writepages Date: Thu, 18 Apr 2019 14:41:10 -0400 Message-Id: <20190418184113.9152-19-hubcap@kernel.org> In-Reply-To: <20190418184113.9152-1-hubcap@kernel.org> References: <20190418184113.9152-1-hubcap@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk
Series	Orangefs Through the Pagecache \| expand [RFC,00/22] Orangefs Through the Pagecache [01/22] orangefs: implement xattr cache [02/22] orangefs: do not invalidate attributes on inode create [03/22] orangefs: simplify orangefs_inode_getattr interface [04/22] orangefs: update attributes rather than relying on server [05/22] orangefs: hold i_lock during inode_getattr [06/22] orangefs: set up and use backing_dev_info [07/22] orangefs: let setattr write to cached inode [08/22] orangefs: reorganize setattr functions to track attribute changes [09/22] orangefs: remove orangefs_readpages [10/22] orangefs: service ops done for writeback are not killable [11/22] orangefs: migrate to generic_file_read_iter [12/22] orangefs: implement writepage [13/22] orangefs: do not return successful read when the client-core disappeared [14/22] orangefs: move do_readv_writev to direct_IO [15/22] orangefs: skip inode writeout if nothing to write [16/22] orangefs: avoid fsync service operation on flush [17/22] orangefs: write range tracking [18/22] orangefs: implement writepages [19/22] orangefs: add orangefs_revalidate_mapping [20/22] orangefs: remember count when reading. [21/22] orangefs: pass slot index back to readpage. [22/22] orangefs: copy Orangefs-sized blocks into the pagecache if possible.

Message ID

20190418184113.9152-19-hubcap@kernel.org (mailing list archive)

State

New, archived

Headers

From: hubcap@kernel.org
To: linux-fsdevel@vger.kernel.org, christoph@lameter.com
Cc: Martin Brandenburg <martin@omnibond.com>,
        Mike Marshall <hubcap@omnibond.com>
Subject: [PATCH 18/22] orangefs: implement writepages
Date: Thu, 18 Apr 2019 14:41:10 -0400
Message-Id: <20190418184113.9152-19-hubcap@kernel.org>
In-Reply-To: <20190418184113.9152-1-hubcap@kernel.org>
References: <20190418184113.9152-1-hubcap@kernel.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-fsdevel-owner@vger.kernel.org
Precedence: bulk

Series

Orangefs Through the Pagecache | expand

Commit Message

hubcap@kernel.org April 18, 2019, 6:41 p.m. UTC

From: Martin Brandenburg <martin@omnibond.com>

Go through pages and look for a consecutive writable region.  After
finding a number of consecutive writable pages or when finding that
the next page's dirty range is not contiguous and cannot be written
as one request, send the write to the server.

The number of pages is determined by the client-core's buffer size.

Signed-off-by: Martin Brandenburg <martin@omnibond.com>
Signed-off-by: Mike Marshall <hubcap@omnibond.com>
---
 fs/orangefs/file.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/fs/orangefs/file.c b/fs/orangefs/file.c
index f409ac5d3410..405449ce4b02 100644
--- a/fs/orangefs/file.c
+++ b/fs/orangefs/file.c
@@ -386,6 +386,7 @@  static int orangefs_file_release(struct inode *inode, struct file *file)
 			gossip_debug(GOSSIP_INODE_DEBUG,
 			    "flush_racache finished\n");
 		}
+
 	}
 	return 0;
 }

[18/22] orangefs: implement writepages

Commit Message

Patch