From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>, Li Yu <bingtian.ly@taobao.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Bruce Brutus Curtis <brutus@google.com>,
Weiping Pan <panweiping3@gmail.com>
Subject: Re: What's the status of TCP friends?
Date: Mon, 17 Mar 2014 11:16:05 +0800 [thread overview]
Message-ID: <20140317031605.GA22502@gmail.com> (raw)
In-Reply-To: <1394978619.9668.14.camel@edumazet-glaptop2.roam.corp.google.com>
On Sun, Mar 16, 2014 at 07:03:39AM -0700, Eric Dumazet wrote:
> On Sun, 2014-03-16 at 17:07 +0800, Zheng Liu wrote:
> > Hi all,
> >
> > Until now the TCP friends patch set doesn't be applied. Now what's the
> > status of TCP friends? Is it applicable to be merged into upstream
> > kernel? Any problem that needs to be fixed? Please let me know if I
> > can help.
>
> Well, last attempts showed that while the idea sounded cool,
> implementation opened many races and added quite a lot of complexity in
> fast path.
Thanks for letting me know the current status of this patch set.
>
> We have AF_UNIX with a lot of problems in it, do we really want to bring
> these AF_UNIX problems to AF_INET ?
Please bear with me because I am a newbie. Out of curiosity, what's the
problem in AF_UNIX?
>
> I would rather spend time on AF_UNIX if it doesn't fit your needs right
> now, or consider jumping to KDBUS modern design.
>
> Using AF_INET for IPC is poor choice.
The reason why we use AF_INET for IPC rather than use AF_UNIX is that we
have two applications that need to communicate with each other. They
could be deployed on the same server or different servers. So obviously
if we use AF_INET, we just need to indicate a IP address in config file.
That sounds rational and maintainable for our operation team.
Regards,
- Zheng
next prev parent reply other threads:[~2014-03-17 3:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 9:07 What's the status of TCP friends? Zheng Liu
2014-03-16 14:03 ` Eric Dumazet
2014-03-17 3:16 ` Zheng Liu [this message]
2014-03-18 1:21 ` Hannes Frederic Sowa
2014-03-18 3:13 ` Zheng Liu
2014-03-18 3:52 ` David Miller
2014-03-18 4:03 ` Eric Dumazet
2014-03-18 15:27 ` 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=20140317031605.GA22502@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=bingtian.ly@taobao.com \
--cc=brutus@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=panweiping3@gmail.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).