From: Jens Axboe <axboe@suse.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] block-highmem-all-19
Date: Tue, 18 Jun 2002 14:18:46 +0200 [thread overview]
Message-ID: <20020618121846.GC814@suse.de> (raw)
Hi,
In preparation of 2.4.20-pre, here's an updated version of the
block-highme patch. This enables block drivers to do I/O to high memory
pages instead of reverting to low memory bounce buffers.
Changes:
- (scsi) Fix critical SCpnt->request_buffer -> SCpnt->request.buffer
error
- (scsi) Backport __init_io() changes from 2.5, that enable us to
politely back off on queueing more I/O with any failure. We use this
now instead of reverting to single segment requests on sgtable
allocation failures. For a highmem host this got nasty, because we had
to map the buffer_head and use a bounce buffer for that single segment
anyway. That is now eliminated. Even for non-highmem I/O the single
segment fall back is slower because of the over head associated with
command setup etc.
*.kernel.org/pub/linux/kernel/people/axboe/patches/v2.4/2.4.19-pre10/block-highmem-all-19.bz2
Enjoy,
--
Jens Axboe
reply other threads:[~2002-06-18 12:19 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=20020618121846.GC814@suse.de \
--to=axboe@suse.de \
--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.