From: Christoph Hellwig <hch@ns.caldera.de>
To: linux-lvm@sistina.com
Cc: Anton Blanchard <anton@linuxcare.com.au>,
Mauelshagen@sistina.com, linux-kernel@vger.kernel.org,
lvm@sistina.com
Subject: Re: [linux-lvm] Re: *** ANNOUNCEMENT *** LVM 0.9.1 beta1 available at www.sistina.com
Date: Sat, 13 Jan 2001 17:06:16 +0100 [thread overview]
Message-ID: <20010113170616.B22699@caldera.de> (raw)
In-Reply-To: <20010113114507.D15915@linuxcare.com> <200101130143.f0D1hNF19829@webber.adilger.net>
In-Reply-To: <200101130143.f0D1hNF19829@webber.adilger.net>; from adilger@turbolinux.com on Fri, Jan 12, 2001 at 06:43:23PM -0700
On Fri, Jan 12, 2001 at 06:43:23PM -0700, Andreas Dilger wrote:
> Anton, you write:
> > Have a look at 2.4, arch/sparc64/kernel/ioctl32.c
>
> Yuk.
>
> > Would it be possible to clean up the ioctl interface so we dont need
> > such large hacks for LVM support? I can do the work but I want to be
> > sure you guys will agree to it.
>
> What is the reason for all this? Alignment/wordsize/other? If you look
> at the IOP10 code, much of the in-core data structs were changed to int
> or long, so this sparc code may not be necessary.
The longs are the biggest problem AFAICS.
long is 64bit on sparc64 and 32bit on sparc32...
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-13 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 1:15 *** ANNOUNCEMENT *** LVM 0.9.1 beta1 available at www.sistina.com Heinz J. Mauelshagen
2001-01-13 0:45 ` Anton Blanchard
2001-01-13 1:43 ` Andreas Dilger
2001-01-13 3:00 ` Anton Blanchard
2001-01-13 16:06 ` Christoph Hellwig [this message]
2001-01-14 1:23 ` [linux-lvm] " Anton Blanchard
2001-01-16 8:51 ` Patrick Caulfield
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=20010113170616.B22699@caldera.de \
--to=hch@ns.caldera.de \
--cc=Mauelshagen@sistina.com \
--cc=anton@linuxcare.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@sistina.com \
--cc=lvm@sistina.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