All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Salyzyn <salyzyn@android.com>
To: Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com>,
	tony.luck@intel.com, keescook@chromium.org, anton@enomsg.org,
	ccross@android.com, seiji.aguchi.tr@hitachi.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFD] pstore: pmsg: ramoops: add multiple pmsg instances
Date: Fri, 9 Oct 2015 09:15:02 -0700	[thread overview]
Message-ID: <5617E806.7020407@android.com> (raw)
In-Reply-To: <56171DF4.2030209@hitachi.com>

On 10/08/2015 06:52 PM, Hiraku Toyooka wrote:
> Hello,
>
> I'm trying to make the feature of multiple pmsg instances for ramoops.
I like it, in fact I encourage it.

This is somewhat/exactly what I did when I first created pmsg, but
decided to simplify to one instance for the first release because I was
unsure how many bona fide user space consumers there would be, so kept
the patch small. I kept the instance number 0 around to allow for
expanding this optional feature without introducing incompatibility. But
I sold the idea that multiple writers on single instance can occur if a
common protocol was used. For my own usage (Android) one instance was
more than enough.

Multiple instances does allow one to control individual content aging or
priority, I agree with your assessment, but make sure that you have a
bona fide user for it (even if it is just for yourself)?

NB: ToDo: device tree support for pstore configuration

Thanks

Sincerely -- Mark Salyzyn

  reply	other threads:[~2015-10-09 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09  1:52 [RFD] pstore: pmsg: ramoops: add multiple pmsg instances Hiraku Toyooka
2015-10-09 16:15 ` Mark Salyzyn [this message]
2015-10-19  1:59   ` Hiraku Toyooka

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=5617E806.7020407@android.com \
    --to=salyzyn@android.com \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=hiraku.toyooka.gu@hitachi.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seiji.aguchi.tr@hitachi.com \
    --cc=tony.luck@intel.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.