netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Kumar Gala <galak@gate.crashing.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Andrew Grover <andrew.grover@intel.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	john.ronciak@intel.com, christopher.leech@intel.com
Subject: Re: [RFC] [PATCH 0/3] ioat: DMA engine support
Date: Fri, 9 Dec 2005 10:12:28 +0300	[thread overview]
Message-ID: <20051209071228.GB19920@2ka.mipt.ru> (raw)
In-Reply-To: <Pine.LNX.4.44.0512081606060.24134-100000@gate.crashing.org>

On Thu, Dec 08, 2005 at 04:13:52PM -0600, Kumar Gala (galak@gate.crashing.org) wrote:
> On Wed, 23 Nov 2005, Jeff Garzik wrote:
> 
> > Alan Cox wrote:
> > >>Additionally, current IOAT is memory->memory.  I would love to be able 
> > >>to convince Intel to add transforms and checksums, 
> > > 
> > > 
> > > Not just transforms but also masks and maybe even merges and textures
> > > would be rather handy 8)
> > 
> > 
> > Ah yes:  I totally forgot to mention XOR.
> > 
> > Software RAID would love that.
> 
> A number of embedded processors already have HW that does these kinda of
> things.  On Freescale PPC processors there have been general purpose DMA
> engines for mem<->mem and more recently and additional crypto engines that
> allow for hashing, XOR, and security.
> 
> I'm actually searching for any examples of drivers that deal with the 
> issues related to DMA'ng directly two and from user space memory.
> 
> I have an ioctl based driver that does copies back and forth between user 
> and kernel space and would like to remove that since the crypto engine has 
> full scatter/gather capability.
> 
> The only significant effort I've come across is Peter Chubb's work for 
> user mode drivers which has some code for handling pinning of the user 
> space memory and what looks like generation of a scatter list.

Acrypto supports crypto processing directly in userspace pages.
In 2.6 it is quite easy using get_user_pages().

> - kumar
> 
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
	Evgeniy Polyakov

  parent reply	other threads:[~2005-12-09  7:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-23 20:26 [RFC] [PATCH 0/3] ioat: DMA engine support Andrew Grover
2005-11-23 22:06 ` Jeff Garzik
2005-11-23 22:30   ` Andi Kleen
2005-11-23 23:02     ` Jeff Garzik
2005-11-24  0:05     ` Alan Cox
2005-11-23 23:36       ` Jeff Garzik
2005-11-24  0:17     ` Benjamin LaHaise
2005-11-24  0:50       ` David S. Miller
2005-11-24  6:50       ` Andi Kleen
2005-11-24 15:24         ` Avi Kivity
2005-11-24 15:29           ` Andi Kleen
2005-11-24 15:35             ` Avi Kivity
2005-11-24 15:37               ` Andi Kleen
2005-11-23 22:54   ` Alan Cox
2005-11-23 22:56     ` Jeff Garzik
2005-12-08 22:13       ` Kumar Gala
2005-12-08 22:23         ` Roland Dreier
2005-12-08 22:42         ` Alan Cox
2005-12-09  7:12         ` Evgeniy Polyakov [this message]
2005-11-23 22:45 ` Jeff Garzik
2005-12-02 17:06   ` Jon Mason
2005-11-23 22:53 ` Jeff Garzik
2005-11-23 23:02 ` Alan Cox

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=20051209071228.GB19920@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=andrew.grover@intel.com \
    --cc=christopher.leech@intel.com \
    --cc=galak@gate.crashing.org \
    --cc=jgarzik@pobox.com \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).