From: Al Viro <viro@ZenIV.linux.org.uk>
To: Alex Dubov <alex.dubov@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alex Dubov <oakad@yahoo.com>
Subject: Re: [PATCH 1/2] fs: introduce sendfd() syscall
Date: Wed, 3 Dec 2014 03:40:20 +0000 [thread overview]
Message-ID: <20141203034020.GI29748@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAPs88r8m2QmaOWy623swGk=T3cyG85X3N7Z9tAp3nZvD0Tch+A@mail.gmail.com>
On Wed, Dec 03, 2014 at 01:22:33PM +1100, Alex Dubov wrote:
> On a less related note, I hope you will agree that the simpler
> mechanism for this very in-demand feature is long overdue on Linux
> (every man and his dog are passing fds around these days).
... and I'm less than sure that it's a good thing. If nothing else,
once the pieces of your program are passing descriptors around freely,
you have created a barfball that will be impossible to split between
several boxen if you run into scalability issues. Descriptor-passing
is limited to a single system; you *can't* do that between e.g. components
of a cluster. So it's not an unmixed blessing, just as overuse of
shared memory segments, etc. They do have their uses, but that needs
to be carefully considered every time, or you'll create a major headache
a few years down the road.
next prev parent reply other threads:[~2014-12-03 3:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 4:35 Minimal effort/low overhead file descriptor duplication over Posix.1b s Alex Dubov
2014-12-02 4:35 ` [PATCH 1/2] fs: introduce sendfd() syscall Alex Dubov
2014-12-02 12:50 ` Eric Dumazet
2014-12-02 14:47 ` Alex Dubov
2014-12-02 15:33 ` Eric Dumazet
2014-12-02 16:23 ` Alex Dubov
2014-12-02 16:42 ` Eric Dumazet
2014-12-03 2:11 ` Alex Dubov
2014-12-03 6:48 ` Eric Dumazet
2014-12-02 17:00 ` Al Viro
2014-12-03 2:22 ` Alex Dubov
2014-12-03 3:40 ` Al Viro [this message]
2014-12-03 4:14 ` Alex Dubov
2014-12-03 6:50 ` Eric Dumazet
2014-12-03 8:08 ` Richard Cochran
2014-12-03 8:17 ` Richard Weinberger
2014-12-03 10:41 ` Richard Cochran
2014-12-03 14:08 ` Alex Dubov
2014-12-05 13:37 ` One Thousand Gnomes
2014-12-02 4:35 ` [PATCH 2/2] fs: Wire up sendfd() syscall (all architectures) Alex Dubov
2014-12-02 8:01 ` Geert Uytterhoeven
2014-12-02 8:31 ` Alex Dubov
2014-12-02 11:42 ` Michal Simek
2014-12-02 14:31 ` Alex Dubov
2014-12-02 14:38 ` Geert Uytterhoeven
2014-12-02 15:26 ` Minimal effort/low overhead file descriptor duplication over Posix.1b s Jonathan Corbet
2014-12-02 16:15 ` Alex Dubov
2014-12-17 13:11 ` Kevin Easton
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=20141203034020.GI29748@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=alex.dubov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oakad@yahoo.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