From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"eparis@parisplace.org" <eparis@parisplace.org>,
"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
"arnd@arndb.de" <arnd@arndb.de>,
"hughd@google.com" <hughd@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"cmetcalf@tilera.com" <cmetcalf@tilera.com>,
"yeohc@au1.ibm.com" <yeohc@au1.ibm.com>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"casey@schaufler-ca.com" <casey@schaufler-ca.com>,
"devel@openvz.org" <devel@openvz.org>,
"james.l.morris@oracle.com" <james.l.morris@oracle.com>
Subject: Re: [PATCH v3 08/10] IPC: message queue copy feature introduced
Date: Mon, 13 Aug 2012 14:35:26 +0400 [thread overview]
Message-ID: <5028D86E.9040907@parallels.com> (raw)
In-Reply-To: <CALgW_8VX2pnhohrm6kNA4Ps4COpxVcPV=jNFp+s9O6yj64Vpzw@mail.gmail.com>
12.08.2012 13:48, Manfred Spraul пишет:
> I would keep it simple - unless there is a clear use case where "peek
> by id" is useful.
>
> Or - since MSG_COPY is linux specific anyway:
> What about storing the number of the message that should be returned in *msgp?
> Store it as "int64", just to avoid any 32/64 bit issues.
Sounds reasonable. But, probably, mtype suit better for message number.
I'll update.
--
Best regards,
Stanislav Kinsbursky
prev parent reply other threads:[~2012-08-13 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120810141517.12411.83398.stgit@localhost6.localdomain6>
[not found] ` <20120810142602.12411.63440.stgit@localhost6.localdomain6>
2012-08-11 11:20 ` [PATCH v3 08/10] IPC: message queue copy feature introduced Manfred Spraul
2012-08-11 13:31 ` Stanislav Kinsbursky
2012-08-12 9:48 ` Manfred Spraul
2012-08-13 10:35 ` Stanislav Kinsbursky [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=5028D86E.9040907@parallels.com \
--to=skinsbursky@parallels.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=casey@schaufler-ca.com \
--cc=cmetcalf@tilera.com \
--cc=devel@openvz.org \
--cc=eparis@parisplace.org \
--cc=hpa@zytor.com \
--cc=hughd@google.com \
--cc=james.l.morris@oracle.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=yeohc@au1.ibm.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 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.