netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: hadi@cyberus.ca
Cc: "David S. Miller" <davem@davemloft.net>, netdev <netdev@oss.sgi.com>
Subject: Re: RFC:  Redirect-Device
Date: Thu, 31 Mar 2005 15:56:28 -0800	[thread overview]
Message-ID: <424C8E2C.70302@candelatech.com> (raw)
In-Reply-To: <1112311618.1090.20.camel@jzny.localdomain>

jamal wrote:
> On Thu, 2005-03-31 at 17:54, Ben Greear wrote:
> 
> 
>>No.  I can't imagine a way to make it work with my application.
>>
> I think you are more comfortable with using netdevices and ioctls and
> /proc. 

Definately.  Ever tried to sniff a socket with ethereal? :)

> Why dont we try to help you so you migrate from the approach you are
> currently taking?

Our approaches to the problem are fundamentally different.  I choose
virtual net devices because all my user-space and GUI code that deals
with ethernet & .1q interfaces works with virtual devices.  AND, my
kernel module that can bridge at 990Mbps+ in both directions on a
couple of GigE interfaces also works with any ethernet-like net-device.
(Using raw sockets in user-space I cannot achieve this high of a performance.)

I can also stack virtual devices on other devices (.1q on re-direct devices,
for example).  You may very well be able to do all of these things with
tc, but it would not be worth my time to try to figure out how to change my
entire application over to support a new interface that *might* do what I
need when I can easily add a new virtual net-device that I have already proved
does what I need.

So, I'm not claiming that my code does what you want better than your
code, but I am quite certain that my code does what *I* want better
than your code.

Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2005-03-31 23:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31 20:41 RFC: Redirect-Device Ben Greear
2005-03-31 21:02 ` David S. Miller
2005-03-31 21:05 ` Stephen Hemminger
2005-03-31 21:45   ` Ben Greear
2005-03-31 21:52     ` David S. Miller
2005-03-31 22:04       ` Ben Greear
2005-03-31 22:21         ` David S. Miller
2005-03-31 22:05       ` Stephen Hemminger
2005-03-31 22:26         ` Ben Greear
2005-03-31 22:33           ` David S. Miller
2005-03-31 22:42             ` Ben Greear
2005-03-31 22:43               ` David S. Miller
2005-03-31 21:13 ` jamal
2005-03-31 21:26   ` Ben Greear
2005-03-31 21:53     ` jamal
2005-03-31 22:22       ` Ben Greear
2005-03-31 22:35         ` David S. Miller
2005-03-31 22:54           ` Ben Greear
2005-03-31 23:26             ` jamal
2005-03-31 23:56               ` Ben Greear [this message]
2005-04-01  0:53                 ` jamal
2005-04-01  9:01                 ` bert hubert
2005-04-01 16:58                   ` Ben Greear
2005-03-31 22:46         ` Thomas Graf
2005-03-31 23:00           ` Ben Greear
2005-03-31 23:20         ` jamal
2005-03-31 23:35           ` Ben Greear
2005-03-31 23:46             ` jamal
2005-04-02  8:41   ` Meelis Roos
2005-04-02 21:08     ` jamal
2005-04-01  5:03 ` Pekka Savola
2005-04-01  5:27   ` Ben Greear
2005-04-01  9:28     ` Pekka Savola
2005-04-01 16:29       ` 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=424C8E2C.70302@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --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).