All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lennart Baruschka" <FunFlyer@gmx.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Disabling DMA with ICH10?
Date: Tue, 29 Sep 2009 09:54:16 +0200	[thread overview]
Message-ID: <20090929075416.77960@gmx.net> (raw)
In-Reply-To: <20090928234025.6dc4e3f7@lxorguk.ukuu.org.uk>

Hi, 

On Mon, 2009-09-28 at 23:40 +0100, Alan Cox wrote:
> > 2. My system uses an ICH10 chipset, the harddrive is connected to the
> > Intel SATA controller. Is there a way to disable DMA and switch back to
> > PIO? I tried compiling with libata support and without SCSI support, but
> > the kernel is unable to mount root (no matter if /dev/sda1
> > or /dev/hda1), then.
> 
> If you disable DMA you will make your performance and latency worse not
> better as the PIO transfers will stall the bus and thus the processor.

I thought that PIO transfers (which I understand to be
write32()/read32()'s) unlike DMA transfers could be interrupted by an
high-priority interrupt. Is that wrong?



> If you really are that latency sensitive then the more normal approach
> would be to lock one core for real time use, load the critical code into
> that core CPU cache and run from cache. If you are utterly pushing the
> limit you might even do crazy stuff like use on thread on the core to
> execute RT stuff and the other to issue any I/O accesses that might stall.

Actually, that's what I do - except for locking the page, yet. I do need
to access the PCI bus in real time, though. So I wonder what happens
when the RT CPU is getting data from the PCI device, doing some
calculations on it and then writing back some data to the device,
__while at the same time__ another (non-RT) CPU starts a DMA transfer. I
figured the DMA would block the PCI bus, having my interrupt wait for it
to finish. That's why I'm trying to avoid DMA. 

Please let me know at what point I am mistaken.


Cheers
Lennart

-- 
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

  reply	other threads:[~2009-09-29  7:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28 21:31 Disabling DMA with ICH10? Lennart Baruschka
2009-09-28 20:37 ` Alejandro Riveira Fernández
2009-09-28 22:40 ` Alan Cox
2009-09-29  7:54   ` Lennart Baruschka [this message]
2009-09-29  8:11     ` Arjan van de Ven
2009-09-29 12:29       ` Krzysztof Halasa
2009-09-29 17:05         ` Alan Cox
2009-09-29 20:35           ` Krzysztof Halasa
2009-09-29 22:35             ` Alan Cox
2009-09-30 12:21               ` Krzysztof Halasa
2009-09-29 10:46     ` Alan Cox

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=20090929075416.77960@gmx.net \
    --to=funflyer@gmx.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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.