From: christopherpb@voomtech.com (Christopher Biessener)
To: kernelnewbies@lists.kernelnewbies.org
Subject: driver questions
Date: Wed, 21 Nov 2012 12:11:39 -0600 [thread overview]
Message-ID: <50AD195B.1050603@voomtech.com> (raw)
I have searched using google for information regarding linux driver
development and have found a lot, but not the answers to these questions:
* Can 2 different kernel drivers access the same device at the same time?
* Is every driver known as a kernel module?
Basically I need advice on if I can and how to sidestep some of the
libata device calls. We do not want to replace the entire libata, just
some of it. We have a custom piece of hardware that writes to hard
drives. When we use another one of our devices to act as the host the
client device runs at full speed. When we run the python GUI with our
custom C++ extension using only SATA ports on the motherboard the
program runs at full speed. But when we use the python GUI to drive our
custom hardware we lose 40% of the speed. We believe the speed loss to
be in how libata optimizes how it sends commands/data to the hard
drive/device.
Thanks in advance,
Christopher
next reply other threads:[~2012-11-21 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 18:11 Christopher Biessener [this message]
2012-11-21 23:59 ` driver questions Greg Freemyer
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=50AD195B.1050603@voomtech.com \
--to=christopherpb@voomtech.com \
--cc=kernelnewbies@lists.kernelnewbies.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).