From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Jiang <dave.jiang@intel.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
vkoul@kernel.org, dan.j.williams@intel.com, tony.luck@intel.com,
jing.lin@intel.com, ashok.raj@intel.com,
sanjay.k.kumar@intel.com, megha.dey@intel.com,
jacob.jun.pan@intel.com, yi.l.liu@intel.com, axboe@kernel.dk,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
fenghua.yu@intel.com, hpa@zytor.com
Subject: Re: [PATCH RFC v2 04/14] mm: create common code from request allocation based from blk-mq code
Date: Thu, 12 Dec 2019 16:43:03 -0800 [thread overview]
Message-ID: <20191212164303.7fb6e91c20ffe125f87bda57@linux-foundation.org> (raw)
In-Reply-To: <157617507410.42350.16156693139630931510.stgit@djiang5-desk3.ch.intel.com>
On Thu, 12 Dec 2019 11:24:34 -0700 Dave Jiang <dave.jiang@intel.com> wrote:
> Move the allocation of requests from compound pages to a common function
> to allow usages by other callers.
What other callers are expected?
> Since the routine has more to do with
> memory allocation and management, it is moved to be exported by the
> mempool.h and be part of mm subsystem.
>
Hm, this move doesn't seem to fit very well. But perhaps it's close
enough.
> --- a/mm/Makefile
> +++ b/mm/Makefile
> @@ -42,7 +42,7 @@ obj-y := filemap.o mempool.o oom_kill.o fadvise.o \
> mm_init.o mmu_context.o percpu.o slab_common.o \
> compaction.o vmacache.o \
> interval_tree.o list_lru.o workingset.o \
> - debug.o gup.o $(mmu-y)
> + debug.o gup.o request_alloc.o $(mmu-y)
Now there's a regression. We're adding a bunch of unused code to a
CONFIG_BLOCK=n kernel.
>
> ...
>
> +void request_from_pages_free(struct list_head *page_list)
>
> ...
>
> +int request_from_pages_alloc(void *ctx, unsigned int depth, size_t rq_size,
> + struct list_head *page_list, int max_order,
> + int node,
> + void (*assign)(void *ctx, void *req, int idx))
I find these function names hard to understand. Are they well chosen?
Some documentation would help. These are global, exported-to-modules
API functions and they really should be fully documented.
> +{
> + size_t left;
> + unsigned int i, j, entries_per_page;
> +
> + left = rq_size * depth;
> +
> + for (i = 0; i < depth; ) {
"depth" of what?
> + int this_order = max_order;
> + struct page *page;
> + int to_do;
> + void *p;
> +
> + while (this_order && left < order_to_size(this_order - 1))
> + this_order--;
> +
> + do {
> + page = alloc_pages_node(node,
> + GFP_NOIO | __GFP_NOWARN |
> + __GFP_NORETRY | __GFP_ZERO,
> + this_order);
> + if (page)
> + break;
> + if (!this_order--)
> + break;
> + if (order_to_size(this_order) < rq_size)
> + break;
> + } while (1);
What the heck is all the above trying to do? Some explanatory comments
are needed, methinks.
> + if (!page)
> + goto fail;
> +
> + page->private = this_order;
> + list_add_tail(&page->lru, page_list);
> +
> + p = page_address(page);
> + /*
> + * Allow kmemleak to scan these pages as they contain pointers
> + * to additional allocations like via ops->init_request().
> + */
> + kmemleak_alloc(p, order_to_size(this_order), 1, GFP_NOIO);
> + entries_per_page = order_to_size(this_order) / rq_size;
> + to_do = min(entries_per_page, depth - i);
> + left -= to_do * rq_size;
> + for (j = 0; j < to_do; j++) {
> + assign((void *)ctx, p, i);
> + p += rq_size;
> + i++;
> + }
> + }
> +
> + return i;
> +
> +fail:
> + request_from_pages_free(page_list);
> + return -ENOMEM;
> +}
> +EXPORT_SYMBOL_GPL(request_from_pages_alloc);
next prev parent reply other threads:[~2019-12-13 0:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 18:24 [PATCH RFC v2 00/14] idxd driver for Intel Data Streaming Accelerator Dave Jiang
2019-12-12 18:24 ` [PATCH RFC v2 01/14] x86/asm: add iosubmit_cmds512() based on movdir64b CPU instruction Dave Jiang
2019-12-12 18:24 ` [PATCH RFC v2 02/14] dmaengine: break out channel registration Dave Jiang
2019-12-12 18:24 ` [PATCH RFC v2 03/14] dmaengine: add new dma device registration Dave Jiang
2019-12-12 18:24 ` [PATCH RFC v2 04/14] mm: create common code from request allocation based from blk-mq code Dave Jiang
2019-12-13 0:43 ` Andrew Morton [this message]
2019-12-13 22:06 ` Dave Jiang
2019-12-12 18:24 ` [PATCH RFC v2 05/14] dmaengine: add dma_request support functions Dave Jiang
2019-12-12 18:24 ` [PATCH RFC v2 06/14] dmaengine: add dma request submit and completion path support Dave Jiang
2019-12-12 18:24 ` [PATCH RFC v2 07/14] dmaengine: update dmatest to support dma request Dave Jiang
2019-12-12 18:24 ` [PATCH RFC v2 08/14] dmaengine: idxd: Init and probe for Intel data accelerators Dave Jiang
2019-12-12 18:25 ` [PATCH RFC v2 09/14] dmaengine: idxd: add configuration component of driver Dave Jiang
2019-12-12 18:25 ` [PATCH RFC v2 10/14] dmaengine: idxd: add descriptor manipulation routines Dave Jiang
2019-12-12 18:25 ` [PATCH RFC v2 11/14] dmaengine: idxd: connect idxd to dmaengine subsystem Dave Jiang
2019-12-12 18:25 ` [PATCH RFC v2 12/14] dmaengine: request submit optimization Dave Jiang
2019-12-12 18:25 ` [PATCH RFC v2 13/14] dmaengine: idxd: add char driver to expose submission portal to userland Dave Jiang
2019-12-12 18:25 ` [PATCH RFC v2 14/14] dmaengine: idxd: add sysfs ABI for idxd driver Dave Jiang
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=20191212164303.7fb6e91c20ffe125f87bda57@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ashok.raj@intel.com \
--cc=axboe@kernel.dk \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@intel.com \
--cc=jing.lin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=megha.dey@intel.com \
--cc=mingo@redhat.com \
--cc=sanjay.k.kumar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vkoul@kernel.org \
--cc=yi.l.liu@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®