From: Andrew Morton <akpm@linux-foundation.org>
To: Shannon Nelson <shannon.nelson@intel.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
shannon.nelson@intel.com, dan.j.williams@intel.com,
randy.dunlap@oracle.com
Subject: Re: [PATCH 4/5] I/OAT: Tighten descriptor setup performance
Date: Wed, 17 Oct 2007 17:34:21 -0700 [thread overview]
Message-ID: <20071017173421.2995d0b9.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071018001433.31147.43339.stgit@localhost.localdomain>
On Wed, 17 Oct 2007 17:14:33 -0700
Shannon Nelson <shannon.nelson@intel.com> wrote:
> The change to the async_tx interface cost this driver some performance by
> spreading the descriptor setup across several functions, including multiple
> passes over the new descriptor chain. Here we bring the work back into one
> primary function and only do one pass.
>
> Signed-off-by: Shannon Nelson <shannon.nelson@intel.com>
> ---
>
> drivers/dma/ioat_dma.c | 170 +++++++++++++++++++++++++-----------------------
> drivers/dma/ioatdma.h | 6 +-
> 2 files changed, 93 insertions(+), 83 deletions(-)
>
> diff --git a/drivers/dma/ioat_dma.c b/drivers/dma/ioat_dma.c
> index c44f551..117ac38 100644
> --- a/drivers/dma/ioat_dma.c
> +++ b/drivers/dma/ioat_dma.c
> @@ -46,9 +46,12 @@
> /* internal functions */
> static void ioat_dma_start_null_desc(struct ioat_dma_chan *ioat_chan);
> static void ioat_dma_memcpy_cleanup(struct ioat_dma_chan *ioat_chan);
> +static inline struct ioat_desc_sw *ioat_dma_get_next_descriptor(
> + struct ioat_dma_chan *ioat_chan);
A forward-declared static inline is pretty weird. Does gcc actually do the
right thing with it?
This function is far too large to be inlined anyway.
next prev parent reply other threads:[~2007-10-18 0:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 0:14 [PATCH 1/5] I/OAT: cleanup pci issues Shannon Nelson
2007-10-18 0:14 ` [PATCH 2/5] I/OAT: clean up of dca provider start and stop Shannon Nelson
2007-10-18 0:14 ` [PATCH 3/5] I/OAT: clean up error handling and some print messages Shannon Nelson
2007-10-18 0:14 ` [PATCH 4/5] I/OAT: Tighten descriptor setup performance Shannon Nelson
2007-10-18 0:34 ` Andrew Morton [this message]
2007-10-18 0:41 ` Nelson, Shannon
2007-10-18 0:14 ` [PATCH 5/5] I/OAT: Add completion callback for async_tx interface use Shannon Nelson
2007-10-18 0:37 ` Andrew Morton
2007-10-18 0:46 ` Nelson, Shannon
2007-10-18 0:44 ` Andrew Morton
2007-10-18 0:47 ` David Miller
2007-10-18 0:53 ` Nelson, Shannon
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=20071017173421.2995d0b9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=shannon.nelson@intel.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox