From: Jens Axboe <axboe@suse.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: arjanv@redhat.com, "David S. Miller" <davem@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>
Subject: [patch] block highmem zero bounce v15
Date: Mon, 24 Sep 2001 01:28:01 +0200 [thread overview]
Message-ID: <20010924012801.H2154@suse.de> (raw)
Hi,
I've uploaded a new version of the patch that allows direct I/O to
highmem memory without resorting to bouncing to lower memory. Changes
since last time include:
- Update to 2.4.10
- Fix SCSI dont-merge error. No corruption, just a performance
hit (me)
- Add single_sg_ok entry to SCSI hosts. An alternative solution would be
to always bounce single entry sg for highmem pages, however I don't
want decent drivers to take a hit on account of crap drivers. Now the
entire I/O path should be unaffected for non-highmem enabled
hosts/drivers. (me)
ATM only aic7xxx and sym53c8xxx have single_sg_ok enabled, others will
follow on a per-audit basis.
*.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.10/block-highmem-all-15
--
Jens Axboe
reply other threads:[~2001-09-23 23:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010924012801.H2154@suse.de \
--to=axboe@suse.de \
--cc=arjanv@redhat.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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