From: Jeff Garzik <jgarzik@pobox.com>
To: Anton Blanchard <anton@samba.org>
Cc: Joe Thornber <joe@fib011235813.fsnet.co.uk>,
Linux Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>,
Dave Jones <davej@suse.de>
Subject: Re: [PATCH] Device-mapper submission 6/7
Date: Wed, 16 Oct 2002 11:20:13 -0400 [thread overview]
Message-ID: <3DAD83AD.4000306@pobox.com> (raw)
In-Reply-To: 20021016143822.GA4320@krispykreme
Anton Blanchard wrote:
>>AFAIK Linus and Al Viro (and myself <g>) have always considered ioctls
>>an ugly -ism that should have never made it into Unix. Over and above
>>the Unix/VFS design problems with ioctl(2), ioctl(2) is a pain for
>>people like David Miller who must maintain 32<->64 bit ioctl translation
>>layers for their architecture. ia64 and x64-64 must do this too. Each
>>ioctl you add is an additional headache for them.
>
>
> And ppc64 :) Lately Dave, Andi and I seem to be spending too much time
> bouncing fixes around for 32/64 bit ioctl and syscall translation code.
Tangent: everyone agrees a shared ioctl32 would be immensely useful,
but noone has bothered ;-)
next prev parent reply other threads:[~2002-10-16 15:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 17:58 [PATCH] Device-mapper submission 6/7 Joe Thornber
2002-10-15 18:15 ` Jeff Garzik
2002-10-15 18:59 ` Greg KH
2002-10-15 21:44 ` Joe Thornber
2002-10-16 14:20 ` Jeff Garzik
2002-10-16 14:38 ` Anton Blanchard
2002-10-16 15:20 ` Jeff Garzik [this message]
2002-10-16 15:20 ` Joe Thornber
2002-10-16 15:59 ` Jeff Garzik
2002-10-17 8:05 ` Joe Thornber
2002-10-17 8:26 ` Andi Kleen
2002-10-17 8:50 ` Joe Thornber
2002-10-17 16:54 ` Jeff Garzik
2002-10-18 11:38 ` Jakob Oestergaard
2002-10-17 15:10 ` Jeff Garzik
2002-10-18 0:48 ` Andi Kleen
2002-10-17 0:46 ` Greg KH
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=3DAD83AD.4000306@pobox.com \
--to=jgarzik@pobox.com \
--cc=anton@samba.org \
--cc=davej@suse.de \
--cc=joe@fib011235813.fsnet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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