All of lore.kernel.org
 help / color / mirror / Atom feed
From: RAMON_GARCIA_F <RAMON_GARCIA_F@terra.es>
To: Jan Harkes <jaharkes@cs.cmu.edu>, linux-kernel@vger.kernel.org
Subject: Re: Suggestion for a new system call: convert file handle to a cookie for transfering file handles between processes.)
Date: Mon, 21 Jul 2003 21:06:37 +0200	[thread overview]
Message-ID: <6bda56825e.6825e6bda5@teleline.es> (raw)

I do not understand the first argument. You seem to say it is posible
to create tcpsockets between different computers while it is not useful
to pass cookies under it. I do not see any problem. Just use cookies in
the local system only.

With regard to resource limits, the solution is not too difficult. As
far as resource limits are concernted, a cookie created and not yet
destroyed should count as a file handle owned by the process and user
that created it. That is, a process cannot have more coookies opened and
 not yet consumed plus total open files than the maximum number of
process descriptors. The same for each user id. There is no need for a
new limit.

Apart from the inconvenience of sendmsg being a library function rather
than a system call, I am convinced that it would be posible to implement
unix socket descriptor passing as a library call. This is not posible
for practical reasons of backward compatibility. But that does not
demonstrate that the proposed primitive is not simpler.

Ramon



             reply	other threads:[~2003-07-21 18:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-21 19:06 RAMON_GARCIA_F [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-21 17:04 Suggestion for a new system call: convert file handle to a cookie for transfering file handles between processes.) RAMON_GARCIA_F
2003-07-21 17:27 ` Jan Harkes
2003-07-21 19:31   ` Ingo Oeser

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=6bda56825e.6825e6bda5@teleline.es \
    --to=ramon_garcia_f@terra.es \
    --cc=jaharkes@cs.cmu.edu \
    --cc=linux-kernel@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 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.