From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: Ed Tanous <edtanous@google.com>
Cc: "Bills, Jason M" <jason.m.bills@linux.intel.com>,
openbmc@lists.ozlabs.org
Subject: Re: Adding support for custom SEL records
Date: Mon, 24 Oct 2022 15:03:22 -0400 [thread overview]
Message-ID: <20221024190322.et5kn54vong3tn2v@cheese> (raw)
In-Reply-To: <CAH2-KxDoO4=141nhu2OV-FmyqCCst8_2TSmgvhJP4Ch14vas0A@mail.gmail.com>
This is helpful, thanks Ed.
On Mon, Oct 24, 2022 at 10:59:51AM -0700, Ed Tanous wrote:
>From what I recall, the requirements were:
>- Ability to store 4000 logs in a rotating buffer (original desire was
>10,000, but 4000 was picked as a middle-ground that could be
>implemented).
A DBus object based implementation could meet this requirement, right?
>- Ability to log 100+ entries per second, including when buffers get
>overwritten.
I guess I would not be shocked if DBus objects + serialization might not
be able to sustain this rate of incoming logs. Maybe it depends on the
filesystem or how the data is serialized in the filesystem. The DBus
approach creates many files. Obviously the syslog approach is only
using a couple of files.
Do you think this kind of requirement is typical? Quoting Patrick from
another thread here:
>don't think anyone is intending to create 10k events in the span of
>a minute
100/s is only 6k in a minute but that is getting pretty close...
>- (abstract) Log storage should be aware of hardware limitations (SPI
>flash cell write endurance) and allow writing N logs per minute for
>the lifetime of the machine without hardware failure. (I forget the
>value of N).
Do you think the rsyslog implementation does better at this? Why?
>- "ipmitool sensor list" should return the results from a full sel log
>in less than 1 second (renegotiated from 200ms, the faster the
>better).
Ok, again I would not be shocked if DBus objects weren't able to deliver
on this.
>- The logging implementation should be able to support a well-formed,
>version controlled, Redfish MessageRegistry to the DMTF
>specifications.
Do you think a DBus object based implementation could meet this
requirement?
>- The logging implementation should be able to implement a
>well-formed, stable, and ACID compliant IPMI SEL command
>implementation.
Do you think a DBus object based implementation could meet this
requirement?
>
>I don't believe the current DBus implementation can meet the previous
>requirements,
The motivation of my questions above is to understand which requirements
cannot be met by something based on DBus objects.
Thanks,
brad
next prev parent reply other threads:[~2022-10-24 19:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 7:35 Adding support for custom SEL records Lei Yu
2022-10-18 20:09 ` Brad Bishop
2022-10-19 2:05 ` Lei Yu
2022-10-19 14:43 ` Brad Bishop
2022-10-19 15:50 ` Bills, Jason M
2022-10-19 17:10 ` Brad Bishop
2022-10-19 18:05 ` Bills, Jason M
2022-10-19 20:20 ` Brad Bishop
2022-10-20 13:24 ` Lei Yu
2022-10-20 14:39 ` Deng Tyler
2022-10-24 17:59 ` Ed Tanous
2022-10-24 19:03 ` Brad Bishop [this message]
2022-10-24 20:19 ` Ed Tanous
2022-10-25 20:18 ` Bills, Jason M
2022-10-24 22:56 ` Vernon Mauery
2022-10-21 20:14 ` Patrick Williams
2022-10-24 22:44 ` Vernon Mauery
2022-10-21 20:34 ` Patrick Williams
2022-10-25 20:37 ` Bills, Jason M
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=20221024190322.et5kn54vong3tn2v@cheese \
--to=bradleyb@fuzziesquirrel.com \
--cc=edtanous@google.com \
--cc=jason.m.bills@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
/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.