From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: use __GFP_NOWARN for iod allocation
Date: Thu, 21 Jun 2018 08:06:24 -0700 [thread overview]
Message-ID: <20180621150624.GA1718@infradead.org> (raw)
In-Reply-To: <87f5c54b-dc09-817b-0660-440a75af7407@kernel.dk>
On Thu, Jun 21, 2018@09:02:18AM -0600, Jens Axboe wrote:
> >From a quick look, the fabric code goes through the same nvme_queue_rq()
> and ends up doing the same iod->sg allocation. I don't see any use of
> chained sg lists, we're allocating one big sg table for the command.
nvme_queue_rq is only used for PCIe.
E.g. for RDMA the call is:
nvme_rdma_queue_rq
-> nvme_rdma_map_data
-> sg_alloc_table_chained
similar for FC and loop.
next prev parent reply other threads:[~2018-06-21 15:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 19:10 [PATCH] nvme: use __GFP_NOWARN for iod allocation Jens Axboe
2018-06-20 19:16 ` Jens Axboe
2018-06-20 20:09 ` Jens Axboe
2018-06-20 20:43 ` Keith Busch
2018-06-20 20:54 ` Jens Axboe
2018-06-20 22:30 ` Keith Busch
2018-06-20 22:30 ` Jens Axboe
2018-06-21 7:10 ` Christoph Hellwig
2018-06-21 14:47 ` Jens Axboe
2018-06-21 15:01 ` Christoph Hellwig
2018-06-21 15:04 ` Jens Axboe
2018-06-21 15:06 ` Jens Axboe
2018-06-21 15:24 ` Christoph Hellwig
2018-06-21 15:26 ` Jens Axboe
2018-06-21 15:24 ` Christoph Hellwig
2018-06-21 15:34 ` Jens Axboe
2018-06-21 15:45 ` Christoph Hellwig
2018-06-21 15:49 ` Jens Axboe
2018-06-21 16:27 ` Keith Busch
2018-06-21 17:20 ` Jens Axboe
2018-06-21 17:54 ` Christoph Hellwig
2018-06-21 19:18 ` Jens Axboe
2018-06-20 20:51 ` Jens Axboe
2018-06-21 7:15 ` Christoph Hellwig
2018-06-21 14:37 ` Jens Axboe
2018-06-21 14:56 ` Christoph Hellwig
2018-06-21 15:01 ` Jens Axboe
2018-06-21 7:09 ` Christoph Hellwig
2018-06-21 14:39 ` Jens Axboe
2018-06-21 14:58 ` Christoph Hellwig
2018-06-21 15:02 ` Jens Axboe
2018-06-21 15:06 ` Christoph Hellwig [this message]
2018-06-21 15:11 ` Jens Axboe
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=20180621150624.GA1718@infradead.org \
--to=hch@infradead.org \
/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.