All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: "David S. Miller" <davem@redhat.com>,
	lse-tech@lists.sourceforge.net,
	"Leonard N. Zubkoff" <lnz@dandelion.com>,
	arjanv@redhat.com
Subject: [patch] PCI64 + block zero-bounce highmem v11
Date: Thu, 23 Aug 2001 09:53:24 +0200	[thread overview]
Message-ID: <20010823095324.Q604@suse.de> (raw)

Hi,

Uploaded a new version. Changes since block-highmem-all-10:

- Merge pci64-1 from davem (me)
- Merge pci64-2 from davem (me)
- printk type warning on x86 when HIGHMEM wasn't enabled (me)
- Better comment asm-i386/scatterlist.h
- Add single_segment/highmem comment in scsi_merge (me)
- Include Mark Hemment's no __save_flags/__cli in read bounce
- Convert cciss to pci64 interface (me)

HIGHMEM I/O capable hardware now includes:

- IDE (DMA, PIO will revert to bounce) Basically all low level drivers
- SCSI
	- aic7xxx (new)
	- qlogicfc (64-bit too)
	- sym53c8xx (64-bit too)
	- megaraid
	- IPS
- cpqarray
- cciss (64-bit too)

SCSI drivers are typically easy to convert to support < 4GB I/O, usually
just the can_dma_32 flag needs to be added. Some need a bit more work,
like IPS. Look for references to virt_to_bus on the scatterlist
->address and/or bh->b_data to find obvious highmem breakage. For 64-bit
PCI DMA, take a look at David's modifications to sym53c8xx as a good
reference.

I'll include I2O highmem support in the next release -- haven't started
it yet, but it should be a breeze.

DAC960 would be nice to have as well. Leonard, we talked about
converting it to the pci dma interface some time ago -- did you make
progress on that?

*.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.9/block-highmem-all-11

-- 
Jens Axboe


             reply	other threads:[~2001-08-23  7:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-23  7:53 Jens Axboe [this message]
2001-08-23  8:09 ` [patch] PCI64 + block zero-bounce highmem v11 Jens Axboe
2001-08-23 12:55 ` Alan Cox
2001-08-24  6:39   ` Jens Axboe
2001-08-23 16:33 ` Leonard N. Zubkoff

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=20010823095324.Q604@suse.de \
    --to=axboe@suse.de \
    --cc=arjanv@redhat.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lnz@dandelion.com \
    --cc=lse-tech@lists.sourceforge.net \
    /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.