From: YH <yh@bizmail.com.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: advice
Date: Sun, 04 Sep 2005 10:43:31 +1000 [thread overview]
Message-ID: <431A4333.6000101@bizmail.com.au> (raw)
Hello,
Apologize for off topic questions. While I am working on a device driver
in kernel 2.4.21, I need advices from kernel developers.
1. When the read() or write() is called from user applications, the
driver can either have a static buffer with limited size or dynamic
memory allocation (kmalloc).
The static buffer is simple and reliable, but limited buffer size to
applications.
Personally, I would like to use dynamic kernel memory allocation
(kmalloc), the question is whether it could be any issues (reliability)
to frequently call kmalloc / kfree in a high speed device (100mpbs)?
2. Although there is a mechanism for user applications to access the
driver through function call read(), write(), or ioctl(). Can the
application passes a callback pointer to the driver in kernel space so
that the driver can call the callback function when some special event
is received. Or if there is a mechanism to let the driver to send a
notification to the user application?
Thank you and appreciate your helps.
Jim
next reply other threads:[~2005-09-04 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 0:43 YH [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-24 19:45 Advice Mr ken Titoh
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=431A4333.6000101@bizmail.com.au \
--to=yh@bizmail.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®