From: Michael Tokarev <mjt@tls.msk.ru>
To: nicolas sitbon <nicolas.sitbon@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: epoll_ctl and const correctness
Date: Sat, 28 Mar 2009 02:01:26 +0300 [thread overview]
Message-ID: <49CD5AC6.3020806@msgid.tls.msk.ru> (raw)
In-Reply-To: <84a01a8b0903271555i7a4fea50nd95009539aa2f94d@mail.gmail.com>
nicolas sitbon wrote:
> Do you read my post? there is a confusion, my question was first : why
> the structure isn't const? and you answer me. ok. second, I asked if
> the kernel keep track of this structure, that is, it keeps a pointer
> on it for doing his job? according to your last answer, no. last
> question : why the size type of the first parameter of epoll_create is
> int and not size_t? no answer for the moment.
Why can't you ask all your questions at once?
The answer to your last one is in the manpage. size_t, as
name suggests, is used for sizes of various memory regions,
in bytes. Here, we're dealing with something else, not bytes.
And probably the next question will be of the sort why the argument
is named 'event' and not 'Event' or 'EventPtr', and why there's no
space after the star character... Oh well.
/mjt
next prev parent reply other threads:[~2009-03-27 23:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 12:45 epoll_ctl and const correctness nicolas sitbon
2009-03-25 16:23 ` Davide Libenzi
2009-03-25 17:27 ` nicolas sitbon
2009-03-27 19:43 ` nicolas sitbon
2009-03-25 21:21 ` Jeremy Fitzhardinge
2009-03-25 21:37 ` nicolas sitbon
2009-03-27 9:44 ` nicolas sitbon
2009-03-27 21:47 ` Michael Tokarev
2009-03-27 22:17 ` nicolas sitbon
2009-03-27 22:30 ` nicolas sitbon
2009-03-27 22:40 ` Davide Libenzi
2009-03-27 22:42 ` Michael Tokarev
2009-03-27 22:55 ` nicolas sitbon
2009-03-27 23:01 ` Michael Tokarev [this message]
2009-03-27 23:10 ` nicolas sitbon
2009-03-27 23:16 ` Michael Tokarev
2009-03-27 23:25 ` nicolas sitbon
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=49CD5AC6.3020806@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.sitbon@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