public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: David Mansfield <lkml@dm.ultramaster.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: cdrom changes in test13-pre2 slow down cdrom access by 70%
Date: Wed, 27 Dec 2000 06:38:10 +0100	[thread overview]
Message-ID: <20001227063810.E5981@suse.de> (raw)
In-Reply-To: <3A43D48D.B1825354@dm.ultramaster.com> <20001223133737.D300@suse.de> <3A4904CA.EA1062AF@dm.ultramaster.com> <3A4911ED.95A73903@dm.ultramaster.com>
In-Reply-To: <3A4911ED.95A73903@dm.ultramaster.com>; from lkml@dm.ultramaster.com on Tue, Dec 26, 2000 at 04:47:25PM -0500

On Tue, Dec 26 2000, David Mansfield wrote:
> > > > The cdrom changes that went into test13-pre2 really kill the performance
> > > > of my cdrom.  I'm using cdparanoia to read audio data, and it normally
> 
> ... cut ...
> 
> > Anyway, do you think a 'try to allocate 8, if that fails, try to
> > allocate 1' solution would be a simple compromise?  That should be easy
> > to do, based on the above code (if kmalloc returns NULL && frames > 1,
> > frames = 1, retry...).
> > 
> 
> Jens, 
> 
> Here's a version of the above idea, ontop of the patch you sent.  It's
> cut and pasted, but I don't think it's whitespace mangled...  I haven't
> actually run with this patch, but it does compile :-)

In principle it looks ok, but after some time we are bound to fail 8
frame allocations anyway and this patch won't help. For the modular
case, preallocation of a bigger chunk at init time is no good either.
Builtin would be fine of course. This almost screams sg to me :-)

-- 
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-27  6:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-22 22:24 cdrom changes in test13-pre2 slow down cdrom access by 70% David Mansfield
2000-12-23 12:37 ` Jens Axboe
2000-12-26 20:51   ` David Mansfield
2000-12-26 21:47     ` David Mansfield
2000-12-27  5:38       ` Jens Axboe [this message]
2000-12-27 16:06         ` David Mansfield
2000-12-27 16:14           ` 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=20001227063810.E5981@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@dm.ultramaster.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