Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754286AbaAUWPl (ORCPT ); Tue, 21 Jan 2014 17:15:41 -0500 Received: from mail.linux-iscsi.org ([67.23.28.174]:34781 "EHLO linux-iscsi.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752402AbaAUWPj (ORCPT ); Tue, 21 Jan 2014 17:15:39 -0500 Message-ID: <1390342665.5567.776.camel@haakon3.risingtidesystems.com> Subject: Re: [PATCH-v2 10/17] target: Add protection SGLs to target_submit_cmd_map_sgls From: "Nicholas A. Bellinger" To: Sagi Grimberg Cc: "Nicholas A. Bellinger" , target-devel , linux-scsi , linux-kernel , "Martin K. Petersen" , Christoph Hellwig , Hannes Reinecke , Sagi Grimberg , Or Gerlitz , Roland Dreier Date: Tue, 21 Jan 2014 14:17:45 -0800 In-Reply-To: <52DBC145.7040104@dev.mellanox.co.il> References: <1390099480-29013-1-git-send-email-nab@daterainc.com> <1390099480-29013-11-git-send-email-nab@daterainc.com> <52DBC145.7040104@dev.mellanox.co.il> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2014-01-19 at 14:12 +0200, Sagi Grimberg wrote: > On 1/19/2014 4:44 AM, Nicholas A. Bellinger wrote: > > From: Nicholas Bellinger > > > > This patch adds support to target_submit_cmd_map_sgls() for > > accepting 'sgl_prot' + 'sgl_prot_count' parameters for > > DIF protection information. > > > > Note the passed parameters are stored at se_cmd->t_prot_sg > > and se_cmd->t_prot_nents respectively. > > > > Also, update tcm_loop and vhost-scsi fabrics usage of > > target_submit_cmd_map_sgls() to take into account the > > new parameters. > > I didn't see that you added protection allocation to transports that > does not use > target_submit_cmd_map_sgls() - which happens to be iSCSI/iSER/SRP :( > > Don't you think that prot SG allocation should be added also to > target_alloc_sgl()? by then > se_cmd should contain the protection attributes and this routine can > know if it needs to > allocate prot_sg as well. This is how I used it... Yes, this specific bit was left out for the moment as no code in the patch for v3.14 actually uses it.. I'm planning to add it to for-next -> v3.15 code as soon as the merge window closes. --nab -- 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/