From: Sami Kerola <kerolasa@iki.fi>
To: Karel Zak <kzak@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Doug Ledford <dledford@redhat.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-kernel@vger.kernel.org
Subject: Re: ipc: object information data in proc and sysfs
Date: Sun, 25 Nov 2012 11:11:45 +0000 [thread overview]
Message-ID: <CAG27Bk32JN+9ECaH1CEsSBMqLR3KBUMQ-kZdJQ7SJLO8UxzeoA@mail.gmail.com> (raw)
In-Reply-To: <20121120122115.GA2006@x2.net.home>
On Tue, Nov 20, 2012 at 12:21 PM, Karel Zak <kzak@redhat.com> wrote:
> On Mon, Nov 19, 2012 at 04:12:50PM -0800, Andrew Morton wrote:
>> Where's the benefit in switching ipcs over to using /proc?
>>
>> procfs reads are probably slower than the syscalls?
>
> 32bit userspace and 64bit kernel (RHEL ppc64), it seems more reliable
> read from /proc than use the syscalls.
>
> I guess that IPC_64 flag for shmctl() commands is used by libc in 64bit
> userspace only.
It seems there is not much interest to have more IPC information
available in user space. Fair enough, and since nothign is exactly
broken so we can live with this.
prev parent reply other threads:[~2012-11-25 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 12:31 ipc: object information data in proc and sysfs Sami Kerola
2012-11-20 0:12 ` Andrew Morton
2012-11-20 12:21 ` Karel Zak
2012-11-25 11:11 ` Sami Kerola [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=CAG27Bk32JN+9ECaH1CEsSBMqLR3KBUMQ-kZdJQ7SJLO8UxzeoA@mail.gmail.com \
--to=kerolasa@iki.fi \
--cc=akpm@linux-foundation.org \
--cc=dledford@redhat.com \
--cc=kerolasa@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=kzak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.