All of lore.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: maheshk@cdac.in, linux-kernel@vger.kernel.org,
	kernelnewbies@nl.linux.org
Subject: Re: [HOWTO] accessing the DMA mapped data
Date: Fri, 11 May 2007 18:42:51 +0300	[thread overview]
Message-ID: <20070511154251.GJ4523@rhun.ibm.com> (raw)
In-Reply-To: <20070510.044732.38321699.davem@davemloft.net>

On Thu, May 10, 2007 at 04:47:32AM -0700, David Miller wrote:
> From: Mahesh <maheshk@cdac.in>
> Date: Thu, 10 May 2007 17:11:17 +0530
> 
> > Hi, > You haven't given an example of where this might actually
> > happen.  > > The driver is where the DMA mappings almost always
> > occur because > that is the layer that knows the bus technology and
> > therefore > the correct DMA interfaces to call.  > > What kind of
> > driver do you have and what is this upper layer > doing the mappings
> > for you but not giving you a pointer to > the kernel buffer as well?
> > > Here I am dealing with a infiniband (see www.openfabrics.org)
> > network device driver. The layer above the driver is the standard
> > infiniband core interface. Now I have a situation where I need to
> > peek into the packets and do some modifications(some hacking). So I
> > just want know whether I can access the original data region using
> > the bus address generated by the dma_map_single.
> 
> You can't, therefore you need to ask the Inifiniband guys to perhaps
> tweak the infiniband driver interfaces so that you can get at the
> buffer or provide some other mechanism by which you can accomplish
> what you're trying to do.

AFAICR the ipath driver had the same problem, which resulted in the
addition of ib specific DMA-API wrappers. See usage of struct
ipath_dma_mapping_ops in ipath_dma.c.

Cheers,
Muli


  reply	other threads:[~2007-05-11 15:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10  7:58 [HOWTO] accessing the DMA mapped data Mahesh
2007-05-10  8:47 ` David Miller
2007-05-10 11:19   ` Mahesh
2007-05-10 11:32     ` David Miller
2007-05-10 11:41       ` Mahesh
2007-05-10 11:47         ` David Miller
2007-05-11 15:42           ` Muli Ben-Yehuda [this message]
2007-05-10 18:27         ` Roland Dreier

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=20070511154251.GJ4523@rhun.ibm.com \
    --to=muli@il.ibm.com \
    --cc=davem@davemloft.net \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maheshk@cdac.in \
    /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.