From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753279AbcEDPcD (ORCPT ); Wed, 4 May 2016 11:32:03 -0400 Received: from mail-wm0-f42.google.com ([74.125.82.42]:37081 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751289AbcEDPb7 (ORCPT ); Wed, 4 May 2016 11:31:59 -0400 From: "=?UTF-8?q?Javier=20Gonz=C3=A1lez?=" X-Google-Original-From: =?UTF-8?q?Javier=20Gonz=C3=A1lez?= To: mb@lightnvm.io Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, =?UTF-8?q?Javier=20Gonz=C3=A1lez?= Subject: [PATCH 1/4] lightnvm: add sync and close block I/O types Date: Wed, 4 May 2016 17:31:29 +0200 Message-Id: <1462375892-26533-1-git-send-email-javier@cnexlabs.com> X-Mailer: git-send-email 2.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Within a target, I/O requests stem from different paths, which might vary in terms of the data structures being allocated, context, etc. This might impact how the request is treated, or how memory is freed once the bio is completed. Add two different types of I/Os: (i) NVM_IOTYPE_SYNC, which indicates that the I/O is synchronous; and (ii) NVM_IOTYPE_CLOSE_BLK, which indicates that the I/O closes the block to which all the ppas on the request belong to. Signed-off-by: Javier González --- include/linux/lightnvm.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/linux/lightnvm.h b/include/linux/lightnvm.h index 29a6890..6c02209 100644 --- a/include/linux/lightnvm.h +++ b/include/linux/lightnvm.h @@ -11,6 +11,8 @@ enum { NVM_IOTYPE_NONE = 0, NVM_IOTYPE_GC = 1, + NVM_IOTYPE_SYNC = 2, + NVM_IOTYPE_CLOSE_BLK = 4, }; #define NVM_BLK_BITS (16) -- 2.5.0