mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Haverkamp <markh@osdl.org>
To: Jens Axboe <axboe@suse.de>
Cc: Mark Wong <markw@osdl.org>,
	akpm@digeo.com, linux-kernel <linux-kernel@vger.kernel.org>,
	wli@holomorphy.com
Subject: Re: OSDL DBT-2 AS vs. Deadline 2.5.68-mm2
Date: 07 May 2003 10:39:11 -0700	[thread overview]
Message-ID: <1052329151.25135.14.camel@markh1.pdx.osdl.net> (raw)
In-Reply-To: <20030507173637.GQ823@suse.de>

On Wed, 2003-05-07 at 10:36, Jens Axboe wrote:
> On Wed, May 07 2003, markw@osdl.org wrote:
> > On  7 May, Jens Axboe wrote:
> > > On Wed, May 07 2003, markw@osdl.org wrote:
> > >> I've collected some data from STP to see if it's useful or if there's
> > >> anything else that would be useful to collect. I've got some tests
> > >> queued up for the newer patches, but I wanted to put out what I had so
> > >> far.
> > >> 
> > >> 
> > >> METRICS OVER LAST 20 MINUTES:
> > >> --------------- -------- ----- ---- -------- -----------------------------------
> > >> Kernel          Elevator NOTPM CPU% Blocks/s URL                                
> > >> --------------- -------- ----- ---- -------- -----------------------------------
> > >> 2.5.68-mm2      as        1155 94.3   8940.2 http://khack.osdl.org/stp/271356/  
> > >> 2.5.68-mm2      deadline  1255 94.9   9598.7 http://khack.osdl.org/stp/271359/  
> > >> 
> > >> FUNCTIONS SORTED BY TICKS:
> > >> -- ------------------------- ------- ------------------------- -------
> > >>  # as 2.5.68-mm2             ticks   deadline 2.5.68-mm2       ticks  
> > >> -- ------------------------- ------- ------------------------- -------
> > >>  1 default_idle              6103428 default_idle              5359025
> > >>  2 bounce_copy_vec             86272 bounce_copy_vec             97696
> > >>  3 schedule                    63819 schedule                    70114
> > >>  4 __make_request              30397 __blk_queue_bounce          31167
> > >>  5 __blk_queue_bounce          26962 scsi_request_fn             26623
> > >>  6 scsi_request_fn             24845 __make_request              25012
> > > 
> > > uhh nasty, you are spending a lot of time bouncing. How much RAM is in
> > > the machine, and what is the scsi hba?
> > 
> > The system has 4GB of memory and has a DECchip 21554 (aacraid) that the
> > external drives are connected to.  Mark Haverkamp is currently trying to
> > address those bounce buffers.
> 
> aacraid actually looks sane enough. so you should just be able to set
> host->highmem_io and it should work.

That is what I thought, but I wanted to get a machine with lots of
memory to try it out on.

Mark.
-- 
Mark Haverkamp <markh@osdl.org>


  reply	other threads:[~2003-05-07 17:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 16:33 markw
2003-05-07 16:44 ` William Lee Irwin III
2003-05-07 16:47 ` Jens Axboe
2003-05-07 16:59   ` markw
2003-05-07 17:36     ` Jens Axboe
2003-05-07 17:39       ` Mark Haverkamp [this message]
2003-05-07 22:41         ` Zwane Mwaikambo
2003-05-07 16:59 ` Martin Josefsson
2003-05-07 17:32   ` markw
2003-05-08  1:41 ` Nick Piggin
2003-05-08 16:12   ` markw
2003-05-08 16:17     ` Jens Axboe

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=1052329151.25135.14.camel@markh1.pdx.osdl.net \
    --to=markh@osdl.org \
    --cc=akpm@digeo.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markw@osdl.org \
    --cc=wli@holomorphy.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

all inboxes | Powered by JetHome®