From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E3264C43381 for ; Tue, 26 Mar 2019 07:37:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B02BF20830 for ; Tue, 26 Mar 2019 07:37:51 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="Efy2kFg6" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730923AbfCZHhv (ORCPT ); Tue, 26 Mar 2019 03:37:51 -0400 Received: from mail-wr1-f66.google.com ([209.85.221.66]:44357 "EHLO mail-wr1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730605AbfCZHhu (ORCPT ); Tue, 26 Mar 2019 03:37:50 -0400 Received: by mail-wr1-f66.google.com with SMTP id y7so8924754wrn.11 for ; Tue, 26 Mar 2019 00:37:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KK7jHdb+4P0go4uC6oYZqOhjPtOdUX+6icNK4TnwyWc=; b=Efy2kFg6jvSRhvjOOdPtz6VUDOx5RJqKfVNARbSN2nerYj9TPTUzMLdRYNqFgDCjly 9aN32u5Fa9Phct562nh+3wOCpEkOB26kW7Oz+uAqmzqSfG/hau+GgkNx+bPjamhzd+R9 LhzcdpQwXTA0twqbIrFXsM8N3l2C+8nWpM89rx3KRemzDokypM2fx0LXd47JEJ/bKKHL mN6r+f3vmK2YPq8brFm6RMGno25URExsvC2igaV46eJcaFINq8vhrvn9T1+xH6KWratJ RLBTfvHAoLssQ/QoaYm/Tsm00l4x5isSNZ/nRyt959xgCwPx3IjSCYssgqE8vOHyRcP6 VAPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KK7jHdb+4P0go4uC6oYZqOhjPtOdUX+6icNK4TnwyWc=; b=cvRNxKPzPoTwbPWkGD9nSoJX7WYG2AKFhRHGDPSOEJN4LOiJ4kU9I6j3r8u+lcVNcs zVzgcKcXn91gp7rlwGaOemjmFSmlJTI6RmsU6QWZmDJuWfaSQtWeLCXtGYpJPGo2ZKxZ Xd4NWXxV3uQEkA4NroNNDk16padC8VFelIMnZWJt1HY8wSkl7bGMevENaurmExUVvbTb w4J7J8qGSrrVymv8SKtDn7Ietgh+bpfE3/Dz1WZp4ikXo+U8yoRWrMP7WKK0B4YdrNoL AEHSKn8YqDOygYQ5VFdWTgKHvw8IImf4Cf2mFIBvj3rxu3+DeGolCVK/x8uPHmpU57yC aJpg== X-Gm-Message-State: APjAAAW+1tcXxm0yhomuqcBbqB86i0Y0Co8MkOFwQlMX23tXNwusOtsG 7EPtqwgnpkW0/NT9DYlEART4ZsvRcoNqIslyeoQ++eNp X-Google-Smtp-Source: APXvYqzud5Z2Gss3ueu55O4ydeH3MJP6Hmm5KVCSlwqPD7MCvD+9aAai6gL4mz/QwKkAUodlEY98fRPIR7vEjwzGHKE= X-Received: by 2002:a5d:4750:: with SMTP id o16mr18069547wrs.206.1553585869266; Tue, 26 Mar 2019 00:37:49 -0700 (PDT) MIME-Version: 1.0 References: <20190326031928.9499-1-ming.lei@redhat.com> <20190326031928.9499-2-ming.lei@redhat.com> <20190326073622.GA21617@lst.de> In-Reply-To: <20190326073622.GA21617@lst.de> From: Ming Lei Date: Tue, 26 Mar 2019 15:37:36 +0800 Message-ID: Subject: Re: [PATCH 1/4] nvmet: set loop queue's segment boundary mask as PAGE_SIZE - 1 To: Christoph Hellwig Cc: Ming Lei , Yi Zhang , Sagi Grimberg , Chaitanya Kulkarni , stable , linux-nvme Content-Type: text/plain; charset="UTF-8" Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Tue, Mar 26, 2019 at 3:36 PM Christoph Hellwig wrote: > > Note that in many cases allocating larger pages in the other targets > would be useful. Given that you fix the one places where we made a page > size assumption I don't see a great need to limit outselves here. block device backed ns still needs this patch. thanks, Ming Lei