public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: Andrew Morton <akpm@zip.com.au>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Scheduler issue 1, RT tasks ...
Date: Mon, 31 Dec 2001 05:56:47 -0800	[thread overview]
Message-ID: <3C306E9F.24BED14F@mvista.com> (raw)
In-Reply-To: <200112291907.LAA25639@messenger.mvista.com> <3C2EE5DC.6EB60E17@mvista.com> <20011230195500Z284765-18284+9610@vger.kernel.org>

Dieter Nützel wrote:
> 
> On Sunday, 29. December 2001 21:00, you wrote:
> >Dieter Nützel wrote:
> > >
> > > I ask because my MP3/Ogg-Vorbis hiccup during dbench isn't solved anyway.
> > > Running 2.4.17 + preempt + lock-break + 10_vm-21 (AA).
> > > Some wisdom?
> >
> > Please test this elevator patch.  I'll be putting it out more formally
> > in a day or two.  Much more testing is needed yet, but for me, the
> > time to read a 16 megabyte file whilst running dbench 160 falls from
> > three minutes thirty seconds to seven seconds.  (This is a VM thing,
> > not an elevator thing).
> 
> Andrew or anybody else,
> 
> can you please send me a copy directly?
> The version I've extracted from the list is some what broken.
> I am not on LKML 'cause it is to much traffic for such a poor little boy like
> me...;-)
> 
Andrew, 

I think the problem is that the mailer(s) insert new lines.  Is this
right Dieter?  It is certainly a problem for me.

Best to mail as an attachment.
-- 
George           george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Real time sched: http://sourceforge.net/projects/rtsched/

  reply	other threads:[~2001-12-31 13:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200112291907.LAA25639@messenger.mvista.com>
2001-12-30 10:01 ` [RFC] Scheduler issue 1, RT tasks george anzinger
2001-12-30 19:54   ` Dieter Nützel
2001-12-31 13:56     ` george anzinger [this message]
2002-01-01 18:55       ` Dieter Nützel
2001-12-29 19:02 Dieter Nützel
2001-12-29 21:00 ` Andrew Morton
2001-12-29 22:24 ` Davide Libenzi
  -- strict thread matches above, loose matches on Subject: below --
2001-12-28  9:45 Martin Knoblauch
2001-12-29  9:12 ` george anzinger
2001-12-20 21:11 Davide Libenzi
2001-12-20 22:25 ` george anzinger
2001-12-20 22:21   ` Momchil Velikov
2001-12-20 22:57     ` Davide Libenzi
2001-12-21 17:00       ` Mike Kravetz
2001-12-21 17:19         ` Davide Libenzi
2001-12-21 17:33           ` Mike Kravetz
2001-12-21 18:29             ` Davide Libenzi
2001-12-24  0:18         ` Victor Yodaiken
2001-12-24  1:31           ` Davide Libenzi
2001-12-24  5:33             ` Victor Yodaiken
2001-12-24 18:52               ` Davide Libenzi
2001-12-27  3:01                 ` Victor Yodaiken
2001-12-27 17:41                   ` Davide Libenzi
2001-12-28  0:05                     ` Victor Yodaiken
2001-12-28  0:48                       ` Davide Libenzi
2001-12-20 22:36   ` Davide Libenzi
2001-12-24  0:19     ` Victor Yodaiken
2001-12-24  1:20       ` Davide Libenzi
2001-12-27  3:42         ` Victor Yodaiken
2001-12-27 17:48           ` Davide Libenzi

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=3C306E9F.24BED14F@mvista.com \
    --to=george@mvista.com \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /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