mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Daniel Glöckner" <dg@emlix.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/3] Support for fastboot over UDP
Date: Thu, 12 Mar 2020 09:26:33 +0100	[thread overview]
Message-ID: <20200312082633.GH3335@pengutronix.de> (raw)
In-Reply-To: <4b033b70-43b8-0dc4-aee9-77612e3c236b@emlix.com>

On Mon, Mar 09, 2020 at 04:38:05PM +0100, Daniel Glöckner wrote:
> Am 03/09/20 um 08:14 schrieb Sascha Hauer:
> > On Fri, Feb 28, 2020 at 09:48:20PM +0100, Daniel Glöckner wrote:
> >> Contrary to U-Boot it does not send keep alive messages every 30
> >> seconds because everything is executed from a poller.
> > 
> > How does that prevent you from sending keep palive messages? Sending
> > packages from a poller should work.
> 
> When long running functions like cb_erase and cb_flash are executed in a
> poller, we can't currently use another poller to check if it is time to
> send a keep alive message.
> 
> If we add a slice to poller_struct that is checked and then acquired in
> poller_call, it would be possible. But as I wrote, we might then want to
> limit the number of pollers executed "in parallel" because of the
> limited stack space.

That's a good idea. I think the stack space won't be a problem as the
number of pollers running in parallel is limited by the number of
existing pollers.

I have updated the series to do exactly that.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2020-03-12  8:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28 20:48 Daniel Glöckner
2020-02-28 20:48 ` [PATCH 1/3] fastboot: split generic code from USB gadget Daniel Glöckner
2020-03-05  7:25   ` Sascha Hauer
2020-02-28 20:48 ` [PATCH 2/3] fastboot net: implement fastboot over UDP Daniel Glöckner
2020-03-05  7:50   ` Sascha Hauer
2020-03-05 20:15     ` Daniel Glöckner
2020-03-06 19:36       ` Sascha Hauer
2020-02-28 20:48 ` [PATCH 3/3] fastboot net: workaround for receiving before sending Daniel Glöckner
2020-03-05  7:54 ` [PATCH 0/3] Support for fastboot over UDP Sascha Hauer
2020-03-09  7:14 ` Sascha Hauer
2020-03-09 15:38   ` Daniel Glöckner
2020-03-12  8:26     ` Sascha Hauer [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=20200312082633.GH3335@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=dg@emlix.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