From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-embedded@ozlabs•org
Subject: Re: data transfer limit using ioctl()?
Date: Wed, 13 Dec 2006 18:09:02 +0100 [thread overview]
Message-ID: <200612131809.03365.arnd@arndb.de> (raw)
In-Reply-To: <297583.85646.qm@web36607.mail.mud.yahoo.com>
On Wednesday 13 December 2006 10:24, Parav Pandit wrote:
> =A0 How much maximum data transfer should be done using ioctl() to driver?
No, there is no technical limit. Usually, it's considered good style
to transfer only a basic data type with fixed length though, like uint32_t
or loff_t, not a long buffer. You should also make sure you have a fixed
length buffer, and that it's the same size on 32 and 64 bit kernels.
=46or long non-structured transfers, use read/write operations if possible.
> =A0 I can also use the Netlink sockets to transfer data from user to kern=
el.
> =A0 Is there any limit that we should consider for choosing ioctl() to dr=
iver or using netlink sockets?
> =A0 =A0
No, that decision does not depend on the data size mostly, but more on
what you want to do.
Arnd <><
prev parent reply other threads:[~2006-12-13 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 9:24 data transfer limit using ioctl()? Parav Pandit
2006-12-13 17:09 ` Arnd Bergmann [this message]
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=200612131809.03365.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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