Ethernet Bridge development
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: shemminger@osdl.org
Cc: netdev@oss.sgi.com, bridge@osdl.org
Subject: Re: [Bridge] Re: [PATCH] (6/6) bridge: receive path optimization
Date: Thu, 26 May 2005 15:54:01 -0700 (PDT)	[thread overview]
Message-ID: <20050526.155401.18310361.davem@davemloft.net> (raw)
In-Reply-To: <20050526154857.3cb34d11@dxpl.pdx.osdl.net>

From: Stephen Hemminger <shemminger@osdl.org>
Date: Thu, 26 May 2005 15:48:57 -0700

> So the call chain is bounded (ie not related to number of filters)
> but slightly longer.

You're right, thanks for the explanation Stephen.

  reply	other threads:[~2005-05-26 22:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 18:04 [Bridge] [PATCH] (6/6) bridge: receive path optimization Stephen Hemminger
2005-05-26 21:46 ` [Bridge] " David S. Miller
2005-05-26 22:48   ` Stephen Hemminger
2005-05-26 22:54     ` David S. Miller [this message]
2005-05-27  5:57       ` Atul Sabharwal
2005-05-27 15:59         ` Stephen Hemminger

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=20050526.155401.18310361.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bridge@osdl.org \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.org \
    /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