linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: nick@snowman.net
To: "David S. Miller" <davem@redhat.com>
Cc: linux_learning@yahoo.co.uk, linux-kernel@vger.kernel.org,
	linux-c-programming@vger.kernel.org
Subject: Re: this code does not get called in dev.c so do we need it?
Date: Thu, 3 Oct 2002 16:14:10 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0210031613500.12220-100000@ns> (raw)
In-Reply-To: <20021002.171042.42890215.davem@redhat.com>

I'm not sure if this is a dumb question, but why arn't there any in-tree
drivers with support for this?  Is it too ugly to merge?
	Nick

On Wed, 2 Oct 2002, David S. Miller wrote:

> 
> Fast routing, although not implemented in any in-tree drivers,
> does get used by some people who have hacked up drivers to support
> this.
> 
> It allows IPv4 routing to occur right at the level of the device
> driver, it directly pushes an input packet to the output routine
> of the destination device all without leaving the driver.
> 
> This code is used.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

      parent reply	other threads:[~2002-10-03 20:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02 14:02 this code does not get called in dev.c so do we need it? will fitzgerald
2002-10-03  0:10 ` David S. Miller
2002-10-03 11:13   ` will fitzgerald
2002-10-03 11:14     ` David S. Miller
2002-10-03 20:14   ` nick [this message]

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=Pine.LNX.4.21.0210031613500.12220-100000@ns \
    --to=nick@snowman.net \
    --cc=davem@redhat.com \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_learning@yahoo.co.uk \
    /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).