15 Dec
2006
15 Dec
'06
12:35 p.m.
Now that mingo's (et al) RT patches are coming into mainstream, what is
the corporate rationale behind it and the running order of urgency?
I am fishing for some information on; if it is the disk-drives, the
network drivers, the usb stack or something else that I am too ignorant
to have noticed?
What worries me the most, is corner-cases on network, blocking multiple
cpu's.
FYI: I have been asked to set up a bunch of Xeon boxens to serve a VPN
over WiFi, they/we are currently using kernel 2.6.17 (debian etch as of
today.) So this is not stricly about audio, but I would guess all of us
would like some clarification here. After all, we have followed the
evolvement of these patches for quite a few years by now.
--
mvh // Jens M Andreasen
15 Dec
15 Dec
4 p.m.
Jens M Andreasen wrote:
Now that mingo's (et al) RT patches are coming
into mainstream, what is
the corporate rationale behind it and the running order of urgency?
I am fishing for some information on; if it is the disk-drives, the
network drivers, the usb stack or something else that I am too ignorant
to have noticed?
What worries me the most, is corner-cases on network, blocking multiple
cpu's.
Isn't the functionality conditional and selected at configure time? I
wouldn't be too worried about it. It also forces broken drivers to be
fixed which is only a good thing. This is a bit similar to the situation
when kernel pre-emption was introduced.
- Jussi
4:24 p.m.
On Fri, 2006-12-15 at 22:00 +0200, Jussi Laako wrote:
Jens M Andreasen wrote:
Yes, but the pathces are introduced and applied a bit at the time for
each official kernel version. At 2.6.19 we can read mingo's own comment
over at slashdot that 'now 50% has gone in'. Friend of order would like
to what half of which is accepted and why.
Kernel conf is hard enough without knowing what to look for, really!
Now that mingo's (et al) RT patches are
coming into mainstream, what is
the corporate rationale behind it and the running order of urgency?
I am fishing for some information on; if it is the disk-drives, the
network drivers, the usb stack or something else that I am too ignorant
to have noticed?
What worries me the most, is corner-cases on network, blocking multiple
cpu's.
Isn't the functionality conditional and selected at configure time? I
wouldn't be too worried about it. It also forces broken drivers to be
fixed which is only a good thing. This is a bit similar to the situation
when kernel pre-emption was introduced.
- Jussi
--
4:42 p.m.
Just to clearify ...
I believe that the RT patches that have been helpful to us in years,
will also be helpful for corporations, better utilizing their fancy
multiprocessor hardware, avoiding spinning in vain waiting ...
So I am not afraid, no ;-) The PHB's are :-D
On Fri, 2006-12-15 at 21:24 +0100, Jens M Andreasen wrote:
On Fri, 2006-12-15 at 22:00 +0200, Jussi Laako wrote:
--
Jens M Andreasen wrote:
Yes, but the pathces are introduced and applied a bit at the time for
each official kernel version. At 2.6.19 we can read mingo's own comment
over at slashdot that 'now 50% has gone in'. Friend of order would like
to what half of which is accepted and why.
Kernel conf is hard enough without knowing what to look for, really!
>
>
> - Jussi Now that mingo's (et al) RT patches are
coming into mainstream, what is
the corporate rationale behind it and the running order of urgency?
I am fishing for some information on; if it is the disk-drives, the
network drivers, the usb stack or something else that I am too ignorant
to have noticed?
What worries me the most, is corner-cases on network, blocking multiple
cpu's.
Isn't the functionality conditional and selected at configure time? I
wouldn't be too worried about it. It also forces broken drivers to be
fixed which is only a good thing. This is a bit similar to the situation
when kernel pre-emption was introduced. 
16 Dec
16 Dec
10:31 a.m.
On Friday 15 December 2006 21:24, Jens M Andreasen wrote:
On Fri, 2006-12-15 at 22:00 +0200, Jussi Laako wrote:
Can you post a link to the story? A quick search didn't find it here..
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
Jens M Andreasen wrote:
Yes, but the pathces are introduced and applied a bit at the time for
each official kernel version. At 2.6.19 we can read mingo's own comment
over at slashdot that 'now 50% has gone in'. Friend of order would like
to what half of which is accepted and why. Now that mingo's (et al) RT patches are
coming into mainstream, what is
the corporate rationale behind it and the running order of urgency?
I am fishing for some information on; if it is the disk-drives, the
network drivers, the usb stack or something else that I am too ignorant
to have noticed?
What worries me the most, is corner-cases on network, blocking multiple
cpu's.
Isn't the functionality conditional and selected at configure time? I
wouldn't be too worried about it. It also forces broken drivers to be
fixed which is only a good thing. This is a bit similar to the situation
when kernel pre-emption was introduced.
10:50 a.m.
On Sat, 2006-12-16 at 15:33 +0100, Florian Schmidt wrote:
Can you post a link to the story? A quick search
didn't find it here..
Heh, slashcode ain't doing what you thought it was supposed to?
Google can find them all though:
http://slashdot.org/~Ingo+Molnar
That would be the latest 24 comments. There are bits of interresting
information in most of them.
Flo
--
6542
days inactive
6543
days old
linux-audio-dev@lists.linuxaudio.org
6 comments
3 participants
participants (3)
-
Florian Schmidt -
Jens M Andreasen -
Jussi Laako