All of lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 1/4] nvmet: set loop queue's segment boundary mask as PAGE_SIZE - 1
Date: Tue, 26 Mar 2019 08:36:22 +0100	[thread overview]
Message-ID: <20190326073622.GA21617@lst.de> (raw)
In-Reply-To: <20190326031928.9499-2-ming.lei@redhat.com>

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.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
	Yi Zhang <yi.zhang@redhat.com>, Sagi Grimberg <sagi@grimberg.me>,
	Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH 1/4] nvmet: set loop queue's segment boundary mask as PAGE_SIZE - 1
Date: Tue, 26 Mar 2019 08:36:22 +0100	[thread overview]
Message-ID: <20190326073622.GA21617@lst.de> (raw)
In-Reply-To: <20190326031928.9499-2-ming.lei@redhat.com>

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.

  reply	other threads:[~2019-03-26  7:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26  3:19 [PATCH 0/4] nvmet: fix file & block device backed ns Ming Lei
2019-03-26  3:19 ` [PATCH 1/4] nvmet: set loop queue's segment boundary mask as PAGE_SIZE - 1 Ming Lei
2019-03-26  3:19   ` Ming Lei
2019-03-26  7:36   ` Christoph Hellwig [this message]
2019-03-26  7:36     ` Christoph Hellwig
2019-03-26  7:37     ` Ming Lei
2019-03-26  7:37       ` Ming Lei
2019-03-26  7:39       ` Ming Lei
2019-03-26  7:39         ` Ming Lei
2019-03-27  8:15       ` Christoph Hellwig
2019-03-27  8:15         ` Christoph Hellwig
2019-03-27  8:26         ` Ming Lei
2019-03-27  8:26           ` Ming Lei
2019-03-27  8:39           ` Christoph Hellwig
2019-03-27  8:39             ` Christoph Hellwig
2019-03-26  3:19 ` [PATCH 2/4] nvmet: fix computation of io vector number Ming Lei
2019-03-26  3:19   ` Ming Lei
2019-03-26  7:38   ` Christoph Hellwig
2019-03-26  7:38     ` Christoph Hellwig
2019-03-26  7:50     ` Ming Lei
2019-03-26  7:50       ` Ming Lei
2019-03-27  8:15       ` Christoph Hellwig
2019-03-27  8:15         ` Christoph Hellwig
2019-03-26  3:19 ` [PATCH 3/4] nvmet: fix computation of bvec->bv_len Ming Lei
2019-03-26  3:19   ` Ming Lei
2019-03-26  3:19 ` [PATCH 4/4] nvmet: build bvec from sg directly Ming Lei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190326073622.GA21617@lst.de \
    --to=hch@lst.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.