All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Heinz <creatix@hipac.org>
To: Laszlo Valko <valko@linux.karinthy.hu>
Cc: Anders Fugmann <afu@fugmann.dhs.org>,
	netfilter-devel@lists.netfilter.org
Subject: Re: Comments about IPT_ALIGN
Date: Mon, 27 Jan 2003 11:33:55 +0100	[thread overview]
Message-ID: <3E350B13.8010502@hipac.org> (raw)
In-Reply-To: 20030127014304.A10076@linux.karinthy.hu

Hi Laszlo

You wrote:
> On sparc, it happens to be the same. I'm not sure how much pure luck
> or intention this is.

Good point. Maybe someone else can enlighten us.

> This might even be a function of using different compiler options...

Ok. If we have to deal with user and kernel space having different
alignment requirements for types of the same bit width but endianness
can be assumed to stay (at least for solution 1)) the same we have
(at least) two options:

1) Define a set of types with fixed bit width and fixed alignment
    requirements for each architecture which must also be made
    available in userspace (which implies that different type
    primitives might be used). The kernel-user structs may only use
    these types as basic types.

2) Define the kernel-user communication in terms of a network protocol
    (anyway, I guess this will be the case if netfilter communication is
    converted to netlink).

> I think the "strictest alignment on this platform" should not come
> from the compiler. It should be defined in some kernel header under
> linux/include/asm-*.

If one cannot make the necessary assumptions this is of course the only
way to define it properly.


Regards,

Thomas

  reply	other threads:[~2003-01-27 10:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-26  3:57 Comments about IPT_ALIGN Thomas Heinz
2003-01-26 11:01 ` Laszlo Valko
2003-01-26 11:28   ` Anders Fugmann
2003-01-26 13:58     ` Thomas Heinz
2003-01-26 14:26       ` Laszlo Valko
2003-01-26 16:50         ` Thomas Heinz
2003-01-26 19:31           ` Laszlo Valko
2003-01-31 11:51       ` Harald Welte
2003-01-26 14:22     ` Laszlo Valko
2003-01-26 18:05       ` Thomas Heinz
2003-01-26 19:43         ` Laszlo Valko
2003-01-26 23:09           ` Thomas Heinz
2003-01-27  0:43             ` Laszlo Valko
2003-01-27 10:33               ` Thomas Heinz [this message]
2003-01-31 11:57                 ` Harald Welte
2003-01-26 19:48         ` Thomas Heinz
2003-01-31 11:55       ` Harald Welte
2003-01-31 23:37         ` Laszlo Valko
2003-01-26 17:06   ` Thomas Heinz

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=3E350B13.8010502@hipac.org \
    --to=creatix@hipac.org \
    --cc=afu@fugmann.dhs.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=valko@linux.karinthy.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.