All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Brittain <jason@brittainweb.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] enabling bus-master IDE driver
Date: Sat, 06 Nov 2004 23:12:38 -0800	[thread overview]
Message-ID: <418DCAE6.9080803@brittainweb.org> (raw)
In-Reply-To: <1099784807.418d62678be4a@imp5-q.free.fr>

zitu wrote:
> Quoting James Boddington <boddingt@optusnet.com.au>:
> 
>>James Boddington wrote:
>>
>>>I found 2000 is using pio as well.
>>
>>I'll change that. It is with 2000 + sp4. I am getting pio on the primary
>>ide and dma on the secondary ide channel.
> 
> on xp, it's PIO for both. DMA if available only on primary (hdd).
> 
> For linux guest, as root, hdparm -d0/-d1 doesn't work.
> 
> But with the DMA patch, you should see DMA is on with the following:
> 'hdparm /dev/hda'
> It's also visible in /proc/ide/hda/settings :)

Looks like mine (with the patch) shows DMA is off:

/dev/hda:
  multcount	= 16 (on)
  IO_support	=  0 (default 16-bit)
  unmaskirq	=  0 (off)
  using_dma	=  0 (off)
  keepsettings   =  0 (off)
  readonly	=  0 (off)
  readahead	= 256 (on)
  geometry	= 33288/16/63, sectors = 33554432, start = 0

And, I can set the IO_support to 1 with hdparm -c1 /dev/hda,
but, as you say, I can't set using_dma to 1 with
hdparm -d1 /dev/hda.  So, looks like it's off, and I can't turn
it on.  Should the IO_support = 1 help any with disk performance?
It doesn't appear to.

-- 
Jason Brittain

  parent reply	other threads:[~2004-11-07  7:33 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-04 20:35 [Qemu-devel] enabling bus-master IDE driver Simon Frew
2004-11-05 13:32 ` zitu
2004-11-05 15:02   ` zitu
2004-11-06  1:53     ` Jason Brittain
2004-11-06 14:27       ` Johannes Schindelin
2004-11-06 21:52         ` Jason Brittain
2004-11-07  9:03           ` Jens Axboe
2004-11-07  9:21             ` Jens Axboe
2004-11-07  9:38               ` Jens Axboe
2004-11-07 11:01                 ` Hetz Ben Hamo
2004-11-07 11:16                   ` Jens Axboe
2004-11-08 10:15                     ` zitu
2004-11-08 16:51                       ` Andreas Bollhalder
2004-11-09  7:38                     ` Paul Jakma
2004-11-09 10:28                       ` Hetz Ben Hamo
2004-11-09 13:53                         ` Paul Jakma
2004-11-11 17:29                     ` Jason Brittain
2004-11-11 19:06                       ` Jens Axboe
2004-11-11 19:02                         ` Jason Brittain
2004-11-11 19:16                           ` Jens Axboe
2004-11-12  8:42                             ` Jens Axboe
2004-11-07 11:02             ` James Boddington
2004-11-10  1:41             ` James Boddington
2004-11-06 21:57         ` James Boddington
2004-11-06 22:11           ` James Boddington
2004-11-06 23:46             ` zitu
2004-11-07  0:41               ` jeebs
2004-11-07  7:12               ` Jason Brittain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-05 15:37 Juergen Keil
2004-11-05 15:43 ` zitu
2004-11-05 15:45 ` zitu
2004-11-05 15:52   ` Jens Axboe
2004-11-05 16:10     ` zitu
2004-11-05 17:30       ` Damien Mascord
2004-11-12 14:27 Juergen Keil
2004-11-12 18:02 ` Jason Brittain
2004-11-12 19:07 Juergen Keil
2004-11-16 19:41 ` Juergen Lock
2004-11-23  5:12   ` Norikatsu Shigemura
2004-11-25 21:12     ` Juergen Lock
2004-11-26 10:48 Juergen Keil
2004-11-28 20:09 ` Juergen Lock

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=418DCAE6.9080803@brittainweb.org \
    --to=jason@brittainweb.org \
    --cc=qemu-devel@nongnu.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.