All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Gold <jgold@mazunetworks.com>
To: Helge Hafting <helge.hafting@aitel.hist.no>
Cc: Mark Lord <lkml@rtr.ca>, linux-kernel@vger.kernel.org
Subject: Re: Serial Console and Slow SCSI Disk Access?
Date: Mon, 19 Jun 2006 11:14:45 -0400	[thread overview]
Message-ID: <4496BF65.30108@mazunetworks.com> (raw)
In-Reply-To: <4496492A.1030907@aitel.hist.no>

Helge Hafting wrote:
> With nothing attached, any write to the serial device might go
> through a lengthy timeout because of flow control.  [...] But I can't
> see why it'd make scsi disks slower. The scsi host adapter 
> initialization writes some messages of course, but there should be no
> more console accesses during a hdparm test run.

This makes sense to me.  When I attach a serial cable and use that to 
login (I've got agetty running), hdparm produces no console messages 
that I can see using minicom.  Still, the disk throughput is around 1.5 
MB/sec for some reason.  When I disable the serial console in grub.conf 
and reboot I get over 70 MB/sec again.

A combination of out-of-tree patches (mainly network related but also 
one to disable PM_TIMERS) seem to eliminate the issue even with the 
serial console enabled, at least for the moment.  That means I no longer 
have a problem, but the whole thing is mysterious to me.

                                        Jeff

  reply	other threads:[~2006-06-19 15:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12 21:28 Serial Console and Slow SCSI Disk Access? Jeff Gold
2006-06-12 21:39 ` Mark Lord
2006-06-12 22:04   ` Jeff Gold
2006-06-19  6:50     ` Helge Hafting
2006-06-19 15:14       ` Jeff Gold [this message]
2006-06-20  7:11         ` Helge Hafting
2006-06-20 16:20           ` Jeff Gold
2006-06-22  0:32           ` David Lang
2006-06-22 16:18             ` Andrey Melnikoff

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=4496BF65.30108@mazunetworks.com \
    --to=jgold@mazunetworks.com \
    --cc=helge.hafting@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.