From: Tejun Heo <tj@kernel.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Kazimierz Krosman <k.krosman@samsung.com>,
akpm@linux-foundation.org, peter@hurleysoftware.com,
vvs@virtuozzo.com, corbet@lwn.net, arnd@arndb.de,
gregkh@linuxfoundation.org, daniel@zonque.org,
kay.sievers@vrfy.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-api@vger.kernel.org,
k.lewandowsk@samsung.com, m.niesluchow@samsung.com,
richard.weinberger@gmail.com, b.zolnierkie@samsung.com,
luto@amacapital.net, knhoon.baik@samsung.com
Subject: Re: [PATCH v6 0/8] Additional kmsg devices
Date: Sat, 27 Feb 2016 06:54:15 -0500 [thread overview]
Message-ID: <20160227115415.GA3965@htj.duckdns.org> (raw)
In-Reply-To: <20160226144718.GF3305@pathway.suse.cz>
Hello,
On Fri, Feb 26, 2016 at 03:47:18PM +0100, Petr Mladek wrote:
> > Could you explain in more detail what did you mean by IPC problems?
>
> I guess that the idea was to make IPC more effective in general.
> You definitely could not move all functionality that needs IPC
> into the kernel.
1. There are multiple ways to do IPC and I don't think what was
implemented as the comparison is optimal.
2. If that were optimal, we have an a lot larger general IPC problem
than logging. We can't possibly implement custom solution for each
specific IPC use case in kernel.
Thanks.
--
tejun
prev parent reply other threads:[~2016-02-27 11:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 11:53 [PATCH v6 0/8] Additional kmsg devices Kazimierz Krosman
2016-02-24 11:53 ` [PATCH v6 1/8] printk: extract kmsg-related routines from printk.c to kmsg.c Kazimierz Krosman
2016-02-24 11:53 ` [PATCH v6 2/8] printk: add one function for storing log in proper format Kazimierz Krosman
2016-02-24 11:53 ` [PATCH v6 3/8] kmsg: introduce additional kmsg devices support Kazimierz Krosman
2016-02-26 14:05 ` Petr Mladek
2016-02-24 11:53 ` [PATCH v6 4/8] kmsg: add additional buffers support to memory class Kazimierz Krosman
2016-02-24 11:53 ` [PATCH v6 5/8] kmsg: add function for adding and deleting additional buffers Kazimierz Krosman
2016-02-24 11:53 ` [PATCH v6 6/8] kmsg: add ioctl for adding and deleting kmsg* devices Kazimierz Krosman
2016-02-24 11:53 ` [PATCH v6 7/8] kmsg: add ioctl for kmsg* devices operating on buffers Kazimierz Krosman
2016-02-24 11:53 ` [PATCH v6 8/8] kmsg: selftests Kazimierz Krosman
2016-02-25 21:47 ` [PATCH v6 0/8] Additional kmsg devices Tejun Heo
2016-02-26 13:22 ` Kazimierz Krosman
2016-02-26 14:47 ` Petr Mladek
2016-02-27 11:54 ` Tejun Heo [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=20160227115415.GA3965@htj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=corbet@lwn.net \
--cc=daniel@zonque.org \
--cc=gregkh@linuxfoundation.org \
--cc=k.krosman@samsung.com \
--cc=k.lewandowsk@samsung.com \
--cc=kay.sievers@vrfy.org \
--cc=knhoon.baik@samsung.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=m.niesluchow@samsung.com \
--cc=peter@hurleysoftware.com \
--cc=pmladek@suse.com \
--cc=richard.weinberger@gmail.com \
--cc=vvs@virtuozzo.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