From: David Miller <davem@davemloft.net>
To: billfink@mindspring.com
Cc: brutus@google.com, edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2] net-tcp: TCP/IP stack bypass for loopback connections
Date: Tue, 14 Aug 2012 22:39:07 -0700 (PDT) [thread overview]
Message-ID: <20120814.223907.1954070712467723629.davem@davemloft.net> (raw)
In-Reply-To: <20120815012428.c747fa9d.billfink@mindspring.com>
From: Bill Fink <billfink@mindspring.com>
Date: Wed, 15 Aug 2012 01:24:28 -0400
> I see no reason to make it obtuse rather than something more
> descriptive of its function (as opposed to how it's implemented).
I want to live in a world where things are allowed to have some
character, and some slightly amusing names. And that's why we'll
call it TCP friends, thank you very much.
> I do have some concern that since the loopback path through the
> TCP stack won't be heavily exercised anymore, it may be more likely
> for bugs or performance degradations to creep into that code.
Are you kidding me? Most people do not use loopback TCP, they use
TCP to a real external entity. TCP friends only kicks in for
loopback connections.
So, like all of your other concerns, this one is meritless.
next prev parent reply other threads:[~2012-08-15 5:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 0:52 [PATCH v2] net-tcp: TCP/IP stack bypass for loopback connections Bruce "Brutus" Curtis
2012-08-14 3:12 ` [PATCH] TCP/IP stack bypass for loopback connections fix Weiping Pan
2012-08-14 6:31 ` [PATCH v2] net-tcp: TCP/IP stack bypass for loopback connections Bill Fink
2012-08-14 7:37 ` David Miller
2012-08-23 16:41 ` Stephen Clark
2012-08-14 16:19 ` Bruce Curtis
2012-08-15 5:24 ` Bill Fink
2012-08-15 5:39 ` David Miller [this message]
2012-08-15 16:17 ` Bill Fink
2012-08-14 21:22 ` David Miller
2012-08-14 21:45 ` Bruce Curtis
2012-08-14 21:50 ` David Miller
2012-08-23 10:57 ` Pádraig Brady
2012-08-23 11:40 ` Eric Dumazet
2012-09-09 17:54 ` Jan Engelhardt
2012-09-09 21:39 ` 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=20120814.223907.1954070712467723629.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=billfink@mindspring.com \
--cc=brutus@google.com \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).