public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Jackson <jerj@coplanar.net>
To: Rogerio Brito <rbrito@iname.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Newbie] Re: Problem creating filesystem
Date: Thu, 01 Mar 2001 23:16:43 -0500	[thread overview]
Message-ID: <3A9F1EAB.7530DF5C@coplanar.net> (raw)
In-Reply-To: <11dd01c0a04e$98b92e60$f40237d1@MIACFERNANDEZ> <3A9B24BE.69777690@coplanar.net> <20010301225739.A674@iname.com>

Rogerio Brito wrote:

> On Feb 26 2001, Jeremy Jackson wrote:
> > Carlos Fernandez Sanz wrote:
> > > The IDE controller is
> > >   Bus  0, device  17, function  0:
> > >     Unknown mass storage controller: Promise Technology Unknown device (rev
> > > 2).
> > >       Vendor id=105a. Device id=d30.
> > >       Medium devsel.  IRQ 10.  Master Capable.  Latency=32.
> >
> > Unrelated to disk "problem", you might want to set your PCI latency timer in
> > BIOS to 64 or more.

This should be accessible in your BIOS setup.  I'm basing my comments on
one NIC driver complaining in my logs and overriding settings lower that 64;
however the general idea is to trade off latency for throughput.  If I go crazy,
like 192 or so, on *my* system, sound card starts to pop a bit, indicating that
it's fifo buffer is smaller that that and is emptying when other devices
are using the bus at the same time (it's like a timeslice)

>
>
>         Ok, I understand that this is probably off-topic and way too
>         basic, but what exactly would this do, in layman terms? Would
>         the latency being set to 32 result in any potential data
>         corruption?  BTW, to set this quantity, one should use setpci,
>         right?


      reply	other threads:[~2001-03-02  4:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-26 23:48 Problem creating filesystem Carlos Fernandez Sanz
2001-02-27  1:39 ` Guest section DW
2001-02-27  3:53 ` Jeremy Jackson
2001-03-02  1:57   ` [Newbie] " Rogerio Brito
2001-03-02  4:16     ` Jeremy Jackson [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=3A9F1EAB.7530DF5C@coplanar.net \
    --to=jerj@coplanar.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rbrito@iname.com \
    /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