From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] User space to kernel space copy optimization
Date: Sat, 5 Dec 2015 13:40:31 +0530 [thread overview]
Message-ID: <20151205081030.GM1854@localhost> (raw)
In-Reply-To: <564A5057.9080203@codeaurora.org>
On Mon, Nov 16, 2015 at 04:53:27PM -0500, Sinan Kaya wrote:
> One of the things I'm interested in is to use a memcpy capable DMA
> engine HW to optimize user space and kernel space parameter copying.
>
> Of course, this will not be viable for all parameter sizes but I can see
> this being useful. The goal is to save power in the cost of little
> performance.
>
> Before I go and invent my own mechanism, I'd like to have ideas on what
> an acceptable solution would look like. Especially, I'm looking for a
> generic implementation that could plug into any DMA engine HW.
Do you have a proposal on how this generic solution should look like, broad
contours of the design to start off with and we can start from that point
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] User space to kernel space copy optimization
Date: Sat, 5 Dec 2015 13:40:31 +0530 [thread overview]
Message-ID: <20151205081030.GM1854@localhost> (raw)
In-Reply-To: <564A5057.9080203@codeaurora.org>
On Mon, Nov 16, 2015 at 04:53:27PM -0500, Sinan Kaya wrote:
> One of the things I'm interested in is to use a memcpy capable DMA
> engine HW to optimize user space and kernel space parameter copying.
>
> Of course, this will not be viable for all parameter sizes but I can see
> this being useful. The goal is to save power in the cost of little
> performance.
>
> Before I go and invent my own mechanism, I'd like to have ideas on what
> an acceptable solution would look like. Especially, I'm looking for a
> generic implementation that could plug into any DMA engine HW.
Do you have a proposal on how this generic solution should look like, broad
contours of the design to start off with and we can start from that point
--
~Vinod
next prev parent reply other threads:[~2015-12-05 8:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 21:53 [RFC] User space to kernel space copy optimization Sinan Kaya
2015-11-16 21:53 ` Sinan Kaya
2015-11-16 22:57 ` Jiang, Dave
2015-11-16 22:57 ` Jiang, Dave
2015-11-16 23:19 ` Sinan Kaya
2015-11-16 23:19 ` Sinan Kaya
2015-11-17 19:28 ` Jiang, Dave
2015-11-17 19:28 ` Jiang, Dave
2015-12-05 8:10 ` Vinod Koul [this message]
2015-12-05 8:10 ` Vinod Koul
2015-12-06 4:24 ` Sinan Kaya
2015-12-06 4:24 ` Sinan Kaya
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=20151205081030.GM1854@localhost \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.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.