From: Michal Simek <monstr@monstr.eu>
To: netdev@vger.kernel.org
Subject: Hight speed data sending from custom IP out of kernel
Date: Tue, 19 Apr 2011 11:49:21 +0200 [thread overview]
Message-ID: <4DAD5AA1.4000900@monstr.eu> (raw)
Hi,
I would like to create demo for high speed data sending from custom IP through
the ethernet. I think the best description is that there are dmaable memory
mapped registers or just memory which store data I want to send (for example 200MB).
Linux should handle all communication between target(probably server) and host
(client) but data in the packets should go from that custom IP and can't go
through the kernel because of performance issue.
Ethernet core have own DMA which I could use but the question is if there is any
option how to convince the kernel that data will go directly from memory mapped
registers and the kernel/driver/... just setup dma BD for headers and second for
data.
Do you have any experience with any solution with passing data completely out of
kernel?
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next reply other threads:[~2011-04-19 9:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 9:49 Michal Simek [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-19 11:34 Hight speed data sending from custom IP out of kernel juice
2011-04-19 11:50 ` Michal Simek
2011-04-19 16:02 ` juice
2011-04-21 8:02 ` Michal Simek
2011-04-21 8:18 ` Eric Dumazet
2011-04-21 9:20 ` Michal Simek
2011-04-25 11:18 ` Michal Simek
2011-04-25 12:14 ` Eric Dumazet
2011-04-25 12:18 ` Michal Simek
2011-04-25 12:27 ` Eric Dumazet
2011-04-25 12:30 ` Eric Dumazet
2011-04-25 12:48 ` Michal Simek
2011-04-21 13:56 ` zhou rui
2011-04-21 14:31 ` zhou rui
2011-04-21 20:27 ` juice
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=4DAD5AA1.4000900@monstr.eu \
--to=monstr@monstr.eu \
--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).