From: Christoph Hellwig <hch@lst.de>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 04/26] net: add a new sockptr_t type
Date: Thu, 23 Jul 2020 16:44:32 +0000 [thread overview]
Message-ID: <20200723164432.GA20917@lst.de> (raw)
In-Reply-To: <20200723060908.50081-5-hch@lst.de>
On Thu, Jul 23, 2020 at 09:40:27AM -0700, Eric Dumazet wrote:
> I am not sure why you chose sockptr_t for something that really seems generic.
>
> Or is it really meant to be exclusive to setsockopt() and/or getsockopt() ?
>
> If the first user of this had been futex code, we would have used
> futexptr_t, I guess.
It was originally intended to be generic and called uptr_t, based
on me misunderstanding that Linus wanted a file operation for it,
which he absolutely didn't and hate with passion. So the plan is to
only use it for setsockopt for now, although there are some arguments
for also using it in sendmsg/recvmsg. There is no need to use it for
getsockopt.
prev parent reply other threads:[~2020-07-23 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 6:08 [PATCH 04/26] net: add a new sockptr_t type Christoph Hellwig
2020-07-23 15:40 ` Jan Engelhardt
2020-07-23 16:40 ` Eric Dumazet
2020-07-23 16:44 ` Christoph Hellwig [this message]
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=20200723164432.GA20917@lst.de \
--to=hch@lst.de \
--cc=dccp@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 read-only IMAP folder(s) and NNTP newsgroup(s).