From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Emily Shaffer <emilyshaffer@google.com>,
Tom Joseph <tomjose@linux.vnet.ibm.com>,
Jeremy Kerr <jk@ozlabs.org>
Cc: Vernon Mauery <vernon.mauery@linux.intel.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Bradley W Bishop <bradleyb@us.ibm.com>
Subject: Re: IPMI SOL performance
Date: Mon, 19 Mar 2018 09:27:07 -0700 [thread overview]
Message-ID: <87y3iokp44.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAJoAoZnqH=C6Nd-XLtZE=4+AcfFQg53B0GYeTWM_03KJCQEo1w@mail.gmail.com>
Emily Shaffer <emilyshaffer@google.com> writes:
>> Is it a possibility to just increase the petitboot timeout? Do you have an
> idea of how much we are missing it by?
Worst case (may be different currently due to improvements in ipmi
stack) was about 10-15 minutes.
We have different issues on the SSH console though, we can end up
dropping chunks of console output under load (BMC CPU load or high
console usage).
I think Jeremy can relive the trauma of heading into the TTY layer, but
I wonder if the solution here has something to do with having a
end-to-end flow control story.
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2018-03-19 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 11:13 IPMI SOL performance Tom Joseph
2018-03-19 11:17 ` Tom Joseph
2018-03-19 15:39 ` Emily Shaffer
2018-03-19 16:27 ` Stewart Smith [this message]
2018-03-19 18:47 ` Emily Shaffer
2018-03-19 19:03 ` Tom Joseph
2018-03-19 19:08 ` Emily Shaffer
2018-03-19 19:34 ` Kun Yi
2018-03-20 15:20 ` Stewart Smith
2018-03-19 19:35 ` Rob Lippert
2018-03-20 0:35 ` Jeremy Kerr
2018-03-20 10:36 ` Tom Joseph
2018-03-20 10:58 ` Jeremy Kerr
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=87y3iokp44.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=bradleyb@us.ibm.com \
--cc=emilyshaffer@google.com \
--cc=jk@ozlabs.org \
--cc=openbmc@lists.ozlabs.org \
--cc=tomjose@linux.vnet.ibm.com \
--cc=vernon.mauery@linux.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.