From: Heinz-Ado Arnolds <Ado.Arnolds@dhm-systems.de>
To: "Gérard Roudier" <groudier@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.16: running *really* short on DMA buffers
Date: Thu, 06 Dec 2001 10:45:16 +0100 [thread overview]
Message-ID: <3C0F3E2C.D3B7D3C7@web-systems.net> (raw)
In-Reply-To: <20011205182528.D1831-100000@gerard>
Gérard Roudier wrote:
>
> On Wed, 5 Dec 2001, Heinz-Ado Arnolds wrote:
>
> > Hi all,
> >
> > I get the message "kernel: Warning - running *really* short on DMA
> > buffers" frequently with medium to heavy disk i/o (running several
> > tar and/or moving huge directories).
...
> So, they are the allocations internal to the scsi layer that may well
> exhaust the ISA DMA pool. This pool is divided into 512 bytes chunks.
> Under heavy reordering of IOs, it can get very fragmented and much memory
> being wasted as a result.
>
> An immediate solution might be to hack the scsi code for it to allocate
> more memory.
I'm not an experienced kernel hacker. Please help me: would it be right
to increase the constant 2 in
new_dma_sectors = 2 * SECTORS_PER_PAGE;
^
in drivers/scsi/scsi_dma.c, scsi_resize_dma_pool() to 3 or 4 as a first
solution. Or is there an other place I should start?
> The error string in well known since years, so you shouldn't have missed
> it from sources. :-)
Sorry, my stupid fault. For sure, it's in drivers/scsi/scsi_merge.c.
Thanks for your attention
Ado
--
------------------------------------------------------------------------
Heinz-Ado Arnolds Ado.Arnolds@web-systems.net
Websystems GmbH +49 2234 1840-0 (voice)
Max-Planck-Strasse 2, 50858 Koeln, Germany +49 2234 1840-40 (fax)
prev parent reply other threads:[~2001-12-06 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 18:59 2.4.16: running *really* short on DMA buffers Heinz-Ado Arnolds
2001-12-05 17:38 ` Gérard Roudier
2001-12-06 9:45 ` Heinz-Ado Arnolds [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=3C0F3E2C.D3B7D3C7@web-systems.net \
--to=ado.arnolds@dhm-systems.de \
--cc=groudier@free.fr \
--cc=linux-kernel@vger.kernel.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