From: Matthew Wilcox <willy@infradead.org>
To: Tony Battersby <tonyb@cybernetics.com>
Cc: Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Sathya Prakash <sathya.prakash@broadcom.com>,
Chaitra P B <chaitra.basappa@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
iommu@lists.linux-foundation.org, linux-mm@kvack.org,
linux-scsi <linux-scsi@vger.kernel.org>,
MPT-FusionLinux.pdl@broadcom.com
Subject: Re: [PATCH 2/3] dmapool: improve scalability of dma_pool_free
Date: Fri, 27 Jul 2018 08:23:22 -0700 [thread overview]
Message-ID: <20180727152322.GB13348@bombadil.infradead.org> (raw)
In-Reply-To: <cae33099-3147-5014-ab4e-c22a4d66dc49@cybernetics.com>
On Fri, Jul 27, 2018 at 09:23:30AM -0400, Tony Battersby wrote:
> On 07/26/2018 08:07 PM, Matthew Wilcox wrote:
> > If you're up for more major surgery, then I think we can put all the
> > information currently stored in dma_page into struct page. Something
> > like this:
> >
> > +++ b/include/linux/mm_types.h
> > @@ -152,6 +152,12 @@ struct page {
> > unsigned long hmm_data;
> > unsigned long _zd_pad_1; /* uses mapping */
> > };
> > + struct { /* dma_pool pages */
> > + struct list_head dma_list;
> > + unsigned short in_use;
> > + unsigned short offset;
> > + dma_addr_t dma;
> > + };
> >
> > /** @rcu_head: You can use this to free a page by RCU. */
> > struct rcu_head rcu_head;
> >
> > page_list -> dma_list
> > vaddr goes away (page_to_virt() exists)
> > dma -> dma
> > in_use and offset shrink from 4 bytes to 2.
> >
> > Some 32-bit systems have a 64-bit dma_addr_t, and on those systems,
> > this will be 8 + 2 + 2 + 8 = 20 bytes. On 64-bit systems, it'll be
> > 16 + 2 + 2 + 4 bytes of padding + 8 = 32 bytes (we have 40 available).
> >
> >
> offset at least needs more bits, since allocations can be multi-page.
Ah, rats. That means we have to use the mapcount union too:
+++ b/include/linux/mm_types.h
@@ -152,6 +152,11 @@ struct page {
unsigned long hmm_data;
unsigned long _zd_pad_1; /* uses mapping */
};
+ struct { /* dma_pool pages */
+ struct list_head dma_list;
+ unsigned int dma_in_use;
+ dma_addr_t dma;
+ };
/** @rcu_head: You can use this to free a page by RCU. */
struct rcu_head rcu_head;
@@ -174,6 +179,7 @@ struct page {
unsigned int active; /* SLAB */
int units; /* SLOB */
+ unsigned int dma_offset; /* dma_pool */
};
/* Usage count. *DO NOT USE DIRECTLY*. See page_ref.h */
> See the following from mpt3sas:
>
> cat /sys/devices/pci0000:80/0000:80:07.0/0000:85:00.0/pools
> (manually cleaned up column alignment)
> poolinfo - 0.1
> reply_post_free_array pool 1 21 192 1
> reply_free pool 1 1 41728 1
> reply pool 1 1 1335296 1
> sense pool 1 1 970272 1
> chain pool 373959 386048 128 12064
> reply_post_free pool 12 12 166528 12
> ^size^
Wow, that's a pretty weird way to use the dmapool. It'd be more efficient
to just call dma_alloc_coherent() directly.
next prev parent reply other threads:[~2018-07-27 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 18:54 [PATCH 2/3] dmapool: improve scalability of dma_pool_free Tony Battersby
2018-07-26 19:42 ` Matthew Wilcox
2018-07-26 20:06 ` Tony Battersby
2018-07-27 0:07 ` Matthew Wilcox
2018-07-27 13:23 ` Tony Battersby
2018-07-27 15:23 ` Matthew Wilcox [this message]
2018-07-27 19:38 ` Tony Battersby
2018-07-27 21:27 ` Tony Battersby
2018-07-27 21:35 ` Andy Shevchenko
2018-07-27 22:07 ` Tony Battersby
2018-07-30 14:05 ` Tony Battersby
2018-07-26 19:45 ` Andy Shevchenko
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=20180727152322.GB13348@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=chaitra.basappa@broadcom.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sathya.prakash@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.com \
--cc=tonyb@cybernetics.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;
as well as URLs for NNTP newsgroup(s).