From: John Newlin <jnewlin@rawbw.com>
To: linux-kernel@vger.kernel.org
Subject: Network device driver Question
Date: Wed, 26 Nov 2003 08:57:20 -0800 [thread overview]
Message-ID: <3FC4DB70.4090808@rawbw.com> (raw)
I'm working on a driver for a new device. This NIC is on-chip, and
memory mapped.
It can DMA to/from any memory location.
I am trying to optimize the driver such that it there is no need to copy
to/from sk_buff
in the send_packet and on packet receive.
The problem I have is with a CPU that has a writeback cache. When the
send_packet
is called, the data in the sk_buff may be cached. In the driver I can
allocate a page as
uncached and copy to that page, however I am trying to avoid unneeded
copies.
For receive there is a similar problem. When I allocate the sk_buff I
need to invalidate
the caches. That way after a new packet arrives a read from that memory
location will
not hit in the cache and return incorrect data.
Is there some sanctioned way that will work on any architecture to cause
a writeback
of the dcached based on a range of virtual addresses, and similiarly
cause an invalidate?
Thanks,
-John Newlin
jnewlin@rawbw.com
reply other threads:[~2003-11-26 16:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3FC4DB70.4090808@rawbw.com \
--to=jnewlin@rawbw.com \
--cc=linux-kernel@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 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.