linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	linux-man <linux-man@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH manpages] epoll_wait.2: add epoll_pwait2
Date: Tue, 12 Jan 2021 14:05:33 +0100	[thread overview]
Message-ID: <CAKgNAkgCbx8OctQ1xQ4337K=QpARbVPhwroKD6XvbQi9GkOrcw@mail.gmail.com> (raw)
In-Reply-To: <87turmibbs.fsf@oldenburg2.str.redhat.com>

Hi Florian,

On Tue, 12 Jan 2021 at 13:33, Florian Weimer <fweimer@redhat.com> wrote:
>
> * Willem de Bruijn:
>
> > From: Willem de Bruijn <willemb@google.com>
> >
> > Expand the epoll_wait page with epoll_pwait2, an epoll_wait variant
> > that takes a struct timespec to enable nanosecond resolution timeout.
> >
> >     int epoll_pwait2(int fd, struct epoll_event *events,
> >                      int maxevents,
> >                      const struct timespec *timeout,
> >                      const sigset_t *sigset);
>
> Does it really use struct timespec?  With 32-bit times on most 32-bit
> targets?

The type inside the kernel seems to be:

[[
SYSCALL_DEFINE6(epoll_pwait2, int, epfd, struct epoll_event __user *, events,
                int, maxevents, const struct __kernel_timespec __user
*, timeout,

struct __kernel_timespec {
        __kernel_time64_t       tv_sec;                 /* seconds */
        long long               tv_nsec;                /* nanoseconds */
};
]]

So, 64 bits by the look of things.

Thanks,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2021-01-12 13:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12  0:48 [PATCH manpages] epoll_wait.2: add epoll_pwait2 Willem de Bruijn
2021-01-12  7:11 ` Michael Kerrisk (man-pages)
2021-01-12 12:33 ` Florian Weimer
2021-01-12 13:05   ` Michael Kerrisk (man-pages) [this message]
2021-01-12 16:39     ` Willem de Bruijn

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='CAKgNAkgCbx8OctQ1xQ4337K=QpARbVPhwroKD6XvbQi9GkOrcw@mail.gmail.com' \
    --to=mtk.manpages@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@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).