netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shmulik Hen <shmulik.hen@intel.com>
To: "David S. Miller" <davem@redhat.com>, <hadi@cyberus.ca>
Cc: <laurent.deniel@thalesatm.com>, <jgarzik@pobox.com>,
	<bonding-devel@lists.sourceforge.net>, <netdev@oss.sgi.com>
Subject: Re: [Bonding-devel] Re: [SET 2][PATCH 2/8][bonding] Propagating  master'ssettings toslaves
Date: Tue, 12 Aug 2003 17:03:15 +0300	[thread overview]
Message-ID: <200308121703.15567.shmulik.hen@intel.com> (raw)
In-Reply-To: <E791C176A6139242A988ABA8B3D9B38A0251E69F@hasmsx403.iil.intel.com>

On Tuesday 12 August 2003 04:08 pm, David S. Miller wrote:

> Policy belongs strictly at user space.

Regarding bonding, what policies are we talking about ?
run-time ?  config time ?  both ?  other ?
Our current aim is config time only.

> One of the great things about what Jamal spends his time working
> on is finally a strict seperation of the control layer from
> everything else.  And part of this is moving all of the control
> logic into userspace. Once that is accomplished, I can have my
> toilet flush every time a TCP packet is routed through my system
> and this won't crap up the kernel.

What scope are we talking about here ?
2.4 ?  2.6 ?  2.7 ?  other ?
Our current aim is 2.4 and 2.6.

Taking into account the two statements I made above:
Do you think that what we're doing right now might interfere with what 
Jamal is suggesting ?
Wouldn't it be possible to do things the old way first and than 
convert everything to the new way ?
Shouldn't all this be a part of a totally new project like "bonding2"

-- 
| Shmulik Hen   Advanced Network Services  |
| Israel Design Center, Jerusalem          |
| LAN Access Division, Platform Networking |
| Intel Communications Group, Intel corp.  |

       reply	other threads:[~2003-08-12 14:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E791C176A6139242A988ABA8B3D9B38A0251E69F@hasmsx403.iil.intel.com>
2003-08-12 14:03 ` Shmulik Hen [this message]
2003-08-12 14:04   ` [Bonding-devel] Re: [SET 2][PATCH 2/8][bonding] Propagating master'ssettings toslaves David S. Miller
2003-08-12 14:29   ` jamal
2003-08-09 10:29 [SET 2][PATCH 2/8][bonding] Propagating master's settings to slaves Hen, Shmulik
2003-08-11 14:20 ` [Bonding-devel] Re: [SET 2][PATCH 2/8][bonding] Propagating master's settings toslaves Shmulik Hen
2003-08-11 14:34   ` jamal
2003-08-11 16:25     ` Shmulik Hen
2003-08-11 16:43       ` Jeff Garzik
2003-08-11 17:31         ` [Bonding-devel] Re: [SET 2][PATCH 2/8][bonding] Propagating master'ssettings toslaves Laurent DENIEL
2003-08-11 17:43           ` Jeff Garzik
2003-08-12  6:31             ` Laurent DENIEL
2003-08-12 12:59               ` jamal
2003-08-12 13:08                 ` David S. Miller
2003-08-12 14:10                   ` Laurent DENIEL
     [not found]                     ` <1060698412.1063.7.camel@jzny.localdomain>
2003-08-12 14:36                       ` Laurent DENIEL
2003-08-12 15:05                         ` jamal
2003-08-12  2:32           ` jamal

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=200308121703.15567.shmulik.hen@intel.com \
    --to=shmulik.hen@intel.com \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=davem@redhat.com \
    --cc=hadi@cyberus.ca \
    --cc=jgarzik@pobox.com \
    --cc=laurent.deniel@thalesatm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).