From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Sam Hopkins" <s.a.hopkins@gmail.com>
Cc: netdev@vger.kernel.org, christopher.leech@intel.com
Subject: Re: Fwd: dma_skb_copy_datagram_iovec not EXPORTed
Date: Tue, 5 Jun 2007 10:24:27 -0700 [thread overview]
Message-ID: <20070605102427.26dd7fac.randy.dunlap@oracle.com> (raw)
In-Reply-To: <908954150706050756x2c7fbee0o9b9df550a09bffb7@mail.gmail.com>
On Tue, 5 Jun 2007 10:56:58 -0400 Sam Hopkins wrote:
> Hello,
>
> I'm forwarding along a message sent to kernelnewbies as I was directed
> to address my question to this list. I am not a member of netdev, so
> please copy me on all discussion of this topic.
>
> Cheers,
>
> Sam
>
> ---
>
> Greetings,
>
> I am a developer of the kernel AoE (ATA over Ethernet) driver. I am
> attempting to add dma offloading of data receive, following in TCP's
> footsteps via config option NET_DMA. There is a function in
> net/core/user_dma.c, dma_skb_copy_datagram_iovec, that appears to be
> exactly what I need, but this function is not EXPORTed for use by
> external modules.
>
> Since the NET_DMA option is documented as "Network: TCP receive copy
> offload" perhaps it's just an oversight that anyone else might benefit
> from it?
Makes sense to me. Maybe someone in the hierarchy will agree,
or you may need to just send a patch and see if it is accepted.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-06-05 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <908954150706041006v2a429726yd267c06ab42a1107@mail.gmail.com>
2007-06-05 14:56 ` Fwd: dma_skb_copy_datagram_iovec not EXPORTed Sam Hopkins
2007-06-05 17:24 ` Randy Dunlap [this message]
2007-06-08 14:30 ` [PATCH 1/1] make network DMA usable for non-tcp drivers Ed L. Cashin
2007-06-08 19:07 ` Andrew Morton
2007-06-10 16:49 ` Dan Williams
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=20070605102427.26dd7fac.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=christopher.leech@intel.com \
--cc=netdev@vger.kernel.org \
--cc=s.a.hopkins@gmail.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).