All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Fink <billfink@mindspring.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: sclark46@earthlink.net, Bruce Curtis <brutus@google.com>,
	David Miller <davem@davemloft.net>,
	edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH v3] net-tcp: TCP/IP stack bypass for loopback connections
Date: Thu, 20 Sep 2012 12:21:56 -0400	[thread overview]
Message-ID: <20120920122156.44cbfd59.billfink@mindspring.com> (raw)
In-Reply-To: <1348141871.31352.66.camel@edumazet-glaptop>

On Thu, 20 Sep 2012, Eric Dumazet wrote:

> On Thu, 2012-09-20 at 07:28 -0400, Stephen Clark wrote:
> >  
> > Does this mean traffic on the loopback interface will not traverse 
> > netfilter?
> > 
> 
> Yes this was already mentioned.
> 
> Only the SYN / SYNACK messages will
> 
> All data will bypass IP stack, qdisc (if any), loopback driver, and
> netfilter.

These restrictions and any others should be documented in ip-sysctl.txt.

>From Eric's earlier e-mail:

-> no iptables, 
   no qdisc (by default there is no qdisc on lo),
   no loopback stats (ifconfig lo).
   some SNMP stats missing as well (netstat -s)

						-Bill

  reply	other threads:[~2012-09-20 17:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17 18:58 [PATCH v3] net-tcp: TCP/IP stack bypass for loopback connections Bruce "Brutus" Curtis
2012-09-17 20:20 ` Eric Dumazet
2012-09-17 23:08   ` Bruce Curtis
2012-09-19 20:34   ` David Miller
2012-09-19 21:03     ` Eric Dumazet
2012-09-19 21:17       ` David Miller
2012-09-19 21:19       ` Bruce Curtis
2012-09-20 11:28         ` Stephen Clark
2012-09-20 11:51           ` Eric Dumazet
2012-09-20 16:21             ` Bill Fink [this message]
2012-09-20 17:24             ` Rick Jones
2012-09-20 19:41               ` David Miller
2012-09-20 19:30           ` David Miller

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=20120920122156.44cbfd59.billfink@mindspring.com \
    --to=billfink@mindspring.com \
    --cc=brutus@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sclark46@earthlink.net \
    /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.