From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Christopher Larson <clarson@kergoth.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] runqueue: Abstract worker functionality to an object/array
Date: Tue, 16 Aug 2016 14:46:34 +0100 [thread overview]
Message-ID: <1471355194.20391.108.camel@linuxfoundation.org> (raw)
In-Reply-To: <CABcZANnCFXP4vS70_qitWWHru_RoC1uDzpKNU-Zy5D6JGhXxAQ@mail.gmail.com>
On Mon, 2016-08-15 at 10:16 -0700, Christopher Larson wrote:
>
> On Mon, Aug 15, 2016 at 9:58 AM, Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
> > + if w in self.rq.worker:
> > + name = "Worker"
> > + elif w in self.rq.fakeworker:
> > + name = "Fakeroot"
> >
> The concept seems sound, but there's still a fair bit of handling
> which is do this thing for workers and that thing for fake workers,
> makes me think we might want to split out objects to bind the
> workers, their names, and their logic.
I agree and there is certainly room for improvement. I think the patch
as it stands is probably a good first step and there are more that can
be made on top of it, I'm open to them or may get around to it myself
eventually if nobody else does. Part of the trouble I've had in doing
this is not to get distracted from the multi-config work which
necessitated it in the first place!
Cheers,
Richard
next prev parent reply other threads:[~2016-08-16 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 16:58 [PATCH] runqueue: Abstract worker functionality to an object/array Richard Purdie
2016-08-15 17:16 ` Christopher Larson
2016-08-16 13:46 ` Richard Purdie [this message]
2016-08-16 14:58 ` Christopher Larson
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=1471355194.20391.108.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.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.