public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jared Lindsay <cinder.sub@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Best Desktop Patchset for kernel
Date: Tue, 4 Oct 2005 20:40:54 -0700	[thread overview]
Message-ID: <e16d914c0510042040s69f39312p11ae78146b4ca855@mail.gmail.com> (raw)
In-Reply-To: <5bdc1c8b0510041940n455044baq40528066cf7a6a97@mail.gmail.com>

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

Eh? Like to destroy filesystems? Not sure what nitro you're talking about...

On 10/4/05, Mark Knecht <markknecht@gmail.com> wrote:
>
> On 10/4/05, Hemmann, Volker Armin <volker.armin.hemmann@tu-clausthal.de>
> wrote:
> > On Wednesday 05 October 2005 03:37, Jared Lindsay wrote:
> > > I really like nitro-sources. They aren't supported in any official
> way, but
> > > you can find them in the Unsupported Software section on the Gentoo
> Forums.
> > > The current release is 2.6.13.2-nitro1 ("Down with latency"), but I
> would
> > > maybe advise waiting until nitro2 comes out (seppe, the maintainer,
> said it
> > > would hopefully be soon), as it will fix a lagging issue with the ck5
> > > patchset.
> >
> > nitro?
> > aren't that the ones who like to destroy filesystems?
> >
> > btw - lower latency = lower throughput = lower overall performance.
>
> lower latency = lower throughput == YES
>
> lower throughput = lower overall performance == NOT NECESSARILY
>
> It depends on how you measure performance. For me performance means
> that real time audio, such as vocals from a singer, flow through the
> machine without being delayed enough for the singer to hear the delay.
> That's performance since without it the machine is useless.
>
> Granted, I get fewer MIPS, etc., but the machine's performance, as I
> measure it, is higher.
>
> Cheers,
> Mark
>
> --
> gentoo-amd64@gentoo.org mailing list
>
>

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

  reply	other threads:[~2005-10-05  3:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05  0:37 [gentoo-amd64] Best Desktop Patchset for kernel Karol Krizka
2005-10-05  1:04 ` Hemmann, Volker Armin
2005-10-05  1:04 ` Mark Knecht
2005-10-05  1:37   ` Jared Lindsay
2005-10-05  2:35     ` Hemmann, Volker Armin
2005-10-05  2:40       ` Mark Knecht
2005-10-05  3:40         ` Jared Lindsay [this message]
2005-10-05  3:50           ` Taka John Brunkhorst
2005-10-05  4:28           ` Hemmann, Volker Armin
2005-10-05 13:42             ` [gentoo-amd64] " Duncan
2005-10-05 17:26               ` Hemmann, Volker Armin
2005-10-05 18:01                 ` Olivier Crete
2005-10-05 20:24                   ` Hemmann, Volker Armin
2005-10-05 18:24                 ` [gentoo-amd64] " Duncan
2005-10-05 21:54                 ` [gentoo-amd64] " Jared Lindsay
2005-10-06  5:19                   ` [gentoo-amd64] " Duncan
2005-10-06  6:53                     ` Hemmann, Volker Armin
2005-10-06 15:59                       ` [gentoo-amd64] " Duncan
2005-10-06 16:35                         ` Marco Matthies
2005-10-06 21:27                           ` [gentoo-amd64] " Duncan
2005-10-06 20:59                     ` [gentoo-amd64] " Jared Lindsay
2005-10-06 21:42                       ` [gentoo-amd64] " Duncan
2005-10-06 21:47                       ` [gentoo-amd64] " Tres Melton
2005-10-11 22:12 ` [gentoo-amd64] " Billy Holmes

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=e16d914c0510042040s69f39312p11ae78146b4ca855@mail.gmail.com \
    --to=cinder.sub@gmail.com \
    --cc=gentoo-amd64@lists.gentoo.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