priority

priority

[Ankit Jain]

Hi to all

Can anybody tell me whats the difference b/w dynamic
priority and normal scheduling ones in linux.......
its confusing.

thanks to all

ankit jain

Send instant messages to your online friends http://uk.messenger.yahoo.com 
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

PRIORITY

[Phil Blundell]

We had some discussion of this a few weeks ago but I'm not sure it ever
reached a firm conclusion.

Is everyone agreed that the PRIORITY variable does not serve any useful
purpose in oe-core and can/should be removed from the recipes?

p.

Re: PRIORITY

[Koen Kooi]

Op 1 jul 2011, om 11:41 heeft Phil Blundell het volgende geschreven:

> We had some discussion of this a few weeks ago but I'm not sure it ever
> reached a firm conclusion.
> 
> Is everyone agreed that the PRIORITY variable does not serve any useful
> purpose in oe-core and can/should be removed from the recipes?

I have no use for that field, so removing it would be fine by me.

regards,

Koen

Re: PRIORITY

[Richard Purdie]

On Fri, 2011-07-01 at 10:41 +0100, Phil Blundell wrote:
> We had some discussion of this a few weeks ago but I'm not sure it ever
> reached a firm conclusion.
> 
> Is everyone agreed that the PRIORITY variable does not serve any useful
> purpose in oe-core and can/should be removed from the recipes?

I think that was the conclusion, yes. I'll take a patch (or a
commandline I guess).

Cheers,

Richard

Re: PRIORITY

[Phil Blundell]

On Fri, 2011-07-01 at 11:15 +0100, Richard Purdie wrote:
> On Fri, 2011-07-01 at 10:41 +0100, Phil Blundell wrote:
> > We had some discussion of this a few weeks ago but I'm not sure it ever
> > reached a firm conclusion.
> > 
> > Is everyone agreed that the PRIORITY variable does not serve any useful
> > purpose in oe-core and can/should be removed from the recipes?
> 
> I think that was the conclusion, yes. I'll take a patch (or a
> commandline I guess).

I did:

$ find . -regex ".*\.\(bb\|inc\)$" | xargs sed -i '/^PRIORITY = ".*"$/d'

which seemed to produce the desired results.  I can send a patch if you
like but it would be somewhat large and fairly uninteresting.

p.

Re: PRIORITY

[Frans Meulenbroeks]

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

2011/7/1 Phil Blundell <pb@pbcl.net>

> On Fri, 2011-07-01 at 11:15 +0100, Richard Purdie wrote:
> > On Fri, 2011-07-01 at 10:41 +0100, Phil Blundell wrote:
> > > We had some discussion of this a few weeks ago but I'm not sure it ever
> > > reached a firm conclusion.
> > >
> > > Is everyone agreed that the PRIORITY variable does not serve any useful
> > > purpose in oe-core and can/should be removed from the recipes?
> >
> > I think that was the conclusion, yes. I'll take a patch (or a
> > commandline I guess).
>
> I did:
>
> $ find . -regex ".*\.\(bb\|inc\)$" | xargs sed -i '/^PRIORITY = ".*"$/d'
>
> which seemed to produce the desired results.  I can send a patch if you
> like but it would be somewhat large and fairly uninteresting.
>
> I'd suggest a regex that matches for any whitespace in order also to catch
things like:
./libgpevtype/libgpevtype_0.50.bb:PRIORITY    = "optional"

Have fun! Frans

[-- Attachment #2: Type: text/html, Size: 1389 bytes --]

Re: PRIORITY

[Richard Purdie]

On Fri, 2011-07-01 at 11:24 +0100, Phil Blundell wrote:
> On Fri, 2011-07-01 at 11:15 +0100, Richard Purdie wrote:
> > On Fri, 2011-07-01 at 10:41 +0100, Phil Blundell wrote:
> > > We had some discussion of this a few weeks ago but I'm not sure it ever
> > > reached a firm conclusion.
> > > 
> > > Is everyone agreed that the PRIORITY variable does not serve any useful
> > > purpose in oe-core and can/should be removed from the recipes?
> > 
> > I think that was the conclusion, yes. I'll take a patch (or a
> > commandline I guess).
> 
> I did:
> 
> $ find . -regex ".*\.\(bb\|inc\)$" | xargs sed -i '/^PRIORITY = ".*"$/d'
> 
> which seemed to produce the desired results.  I can send a patch if you
> like but it would be somewhat large and fairly uninteresting.

I've gone ahead and pushed such a commit, thanks!

Richard