From: Andi Kleen <ak@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: greearb@candelatech.com, amir.noam@intel.com,
bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com,
hadi@cyberus.ca
Subject: Re: [bonding] Add basic support for dynamic configuration of bond interfaces
Date: Mon, 12 Jan 2004 13:38:16 +0100 [thread overview]
Message-ID: <20040112133816.57993f44.ak@suse.de> (raw)
In-Reply-To: <4001C72E.8030108@pobox.com>
On Sun, 11 Jan 2004 16:59:10 -0500
Jeff Garzik <jgarzik@pobox.com> wrote:
> ioctls are a pain for 32/64-bit emulation layers too. It seems much
> easier to define a netlink protocol family of some sort and communicate
> that way.
Actually that's not true. netlink is far worse for emulation layers when you
break the protocol. e.g. the current ipsec/pf_key protocol is not compatible
on x86-64 and it is near impossible to fix it without major surgery.
With ioctls it would be far easier to fixbecause the infrastructure for emulation
is already there.
-Andi
next prev parent reply other threads:[~2004-01-12 12:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E6F7D288B394A64585E67497E5126BA601F991D1@hasmsx403.iil.intel.com>
2004-01-11 14:28 ` [bonding] Add basic support for dynamic configuration of bond interfaces Amir Noam
2004-01-11 18:30 ` jamal
2004-01-11 19:39 ` Jeff Garzik
2004-01-11 21:34 ` Ben Greear
2004-01-11 21:59 ` Jeff Garzik
2004-01-11 22:50 ` jamal
2004-01-11 22:51 ` Ben Greear
2004-01-12 0:13 ` Jason Lunz
2004-01-13 2:34 ` Jeff Garzik
2004-01-12 12:38 ` Andi Kleen [this message]
2004-01-12 13:51 ` jamal
2004-01-12 15:04 ` Andi Kleen
2004-01-13 12:28 ` jamal
2004-01-13 12:39 ` Andi Kleen
[not found] <E6F7D288B394A64585E67497E5126BA601F991D3@hasmsx403.iil.intel.com>
2004-01-14 15:00 ` Amir Noam
2004-01-08 16:19 Amir Noam
2004-01-11 1:34 ` Jeff Garzik
2004-01-12 17:23 ` Ben Greear
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=20040112133816.57993f44.ak@suse.de \
--to=ak@suse.de \
--cc=amir.noam@intel.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=greearb@candelatech.com \
--cc=hadi@cyberus.ca \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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 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.