| commit | 387aa374551913374e9fac1b7bd1ffec896d5f72 | [log] [tgz] |
|---|---|---|
| author | Mike Frysinger <vapier@chromium.org> | Tue Oct 04 02:23:40 2016 |
| committer | Commit Bot <commit-bot@chromium.org> | Fri Jan 29 07:33:42 2021 |
| tree | 7a2f69d271925735904e8f921ddbc5dbd17e77ac | |
| parent | 2fdafe7ae253f1e6caadc2ca1fcacfecca8b11d1 [diff] |
daisydog: trim heaps once we finished initializing We can tell glibc to release any excess memory it allocated once we hit the main loop as this loop is small and should never really do any more malloc. A minor optimization. BUG=None TEST=CQ passes Change-Id: I10f20e5d816392e41857a2a4f903b0838cb8b0ab Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/daisydog/+/2657814 Tested-by: Mike Frysinger <vapier@chromium.org> Auto-Submit: Mike Frysinger <vapier@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> Commit-Queue: Mike Frysinger <vapier@chromium.org>
GPL Code is copied with explicit permission from Daniel Widyanto:
http://embeddedfreak.wordpress.com/2010/08/23/howto-use-linux-watchdog/
The project name is based on Samsung's “daisy” reference board design and I liked this quote from the daisy dog FAQ:
Daisy Dogs are not persnickety little ankle biters
When this daisydog doesn't run, the machine should reset. :)
An alternative code to start with would have been:
https://dev.openwrt.org/ticket/2270
The watchdog project is alot more complicated than what the Chromium OS project needs.