mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Malte Schröder" <Malte.Schroeder@hanse.net>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.4-ck2
Date: Fri, 26 Mar 2004 19:10:11 +0100	[thread overview]
Message-ID: <200403261910.18293.Malte.Schroeder@hanse.net> (raw)
In-Reply-To: <200403270252.46873.kernel@kolivas.org>

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

I was experiencing "skips" in video while playing mpeg4-video with mplayer 
over a DVB-S-card (that means on-the-fly transcoding from mpeg4 to mpeg1) on 
kernel 2.6.4 with -ck1-patch. I thought it was a problem with mplayer, but it 
went away when I tried -ck2 :)
Nice work.

On Friday 26 March 2004 16:49, Con Kolivas wrote:
> Updated my patchset:
> These are patches designed to improve system responsiveness and add
> features with specific emphasis on the desktop.
>
> http://kernel.kolivas.org
>
> Full feature list:
> am
>  Autoregulates the virtual memory swappiness.
> domains
>  Sched_domains support for better hyperthreading and SMP support including
> my smt nice changes
> stair
>  A complete scheduler policy rewrite for interactivity and responsiveness
> batch
>  Batch scheduling.
> iso
>  Isochronous scheduling.
> cfqioprio
>  Complete Fair Queueing disk scheduler and I/O priorities
> schedioprio
>  Set initial I/O priorities according to cpu scheduling policy and nice
> sng204
>  Supermount-NG v2.0.4
> bs314
>  Bootsplash v3.1.4
> reiser4
>  Reiser4 filesystem
> cddma
>  DMA for cd audio
> grsec
>  Greater security (not included in default patch).
>
>
> Changelog
> Additions:
> + Staircase scheduler - my complete scheduler policy rewrite for
> interactivity built on top of the current O(1) scheduler
> + CD audio DMA
> + Grsec (optional only in experimental dir as it breaks compile if
> disabled)
>
> Changes:
> ~New batch scheduling (idle scheduling) policy from scratch based on new
> scheduler is much simpler and less prone to system starvation issues
> ~New isochronous scheduling (low latency, non real time scheduling for
> non-privileged users)
> ~Updated sched_domains
> ~Updated bootsplash v3.1.4
> ~Updated reiser4 snapshot (2004.03.25)
>
> Unchanged:
> Autoregulated vm swappiness
> Supermount-NG v 2.0.4
> CFQ I/O scheduler with I/O priority support.
>
>
> This is my parting gesture as I'll be on extended leave from 31st March
> till the end of May.
>
> Con
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/

-- 
---------------------------------------
Malte Schröder
MalteSch@gmx.de
ICQ# 68121508
---------------------------------------


[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-03-26 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-26 15:49 2.6.4-ck2 Con Kolivas
2004-03-26 18:10 ` Malte Schröder [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=200403261910.18293.Malte.Schroeder@hanse.net \
    --to=malte.schroeder@hanse.net \
    --cc=MalteSch@gmx.de \
    --cc=kernel@kolivas.org \
    --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

all inboxes | Powered by JetHome®