From: "David S. Miller" <davem@redhat.com>
To: groudier@free.fr
Cc: andrea@suse.de, axboe@suse.de, gibbs@scsiguy.com,
LB33JM16@yahoo.com, linux-kernel@vger.kernel.org
Subject: Re: highmem, aic7xxx, and vfat: too few segs for dma mapping
Date: Wed, 12 Dec 2001 16:26:03 -0800 (PST) [thread overview]
Message-ID: <20011212.162603.28785873.davem@redhat.com> (raw)
In-Reply-To: <20011212210923.I642-100000@gerard>
In-Reply-To: <20011212231936.Q4801@athlon.random> <20011212210923.I642-100000@gerard>
From: Gérard Roudier <groudier@free.fr>
Date: Wed, 12 Dec 2001 21:24:59 +0100 (CET)
A N% loss for the 99% case in order to support the 1% is close to N%
loss. So, each time we bloat or complexify the code with no relevance for
the average case, the overall difference cannot be a win.
Do you know, you can use this N% loss to implement handling of the
very problem you have wrt. sym53c8xx hw bugs? :-)
To be honest all the machinery to handle the problems you have
described are there today, even with IOMMU's present. The generic
block layer today knows when IOMMU is being used, it knows what kind
of coalescing can and will be done by the IOMMU support code (via
DMA_CHUNK_SIZE), and therefore it is capable of adhering to any
restrictions you care to describe to the block layer.
It's only a matter of coding on Jens's part :-)
next prev parent reply other threads:[~2001-12-13 0:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 1:32 highmem, aic7xxx, and vfat: too few segs for dma mapping LBJM
2001-12-10 18:40 ` Justin T. Gibbs
2001-12-10 19:21 ` Jens Axboe
2001-12-10 19:50 ` Justin T. Gibbs
2001-12-10 20:03 ` Jens Axboe
2001-12-10 19:21 ` Gérard Roudier
2001-12-11 6:12 ` David S. Miller
2001-12-11 17:01 ` Gérard Roudier
2001-12-12 9:36 ` Jens Axboe
2001-12-12 13:32 ` Andrea Arcangeli
2001-12-12 17:22 ` Gérard Roudier
2001-12-12 22:19 ` Andrea Arcangeli
2001-12-12 20:24 ` Gérard Roudier
2001-12-13 0:26 ` David S. Miller [this message]
2001-12-13 16:17 ` Gérard Roudier
2001-12-13 20:30 ` David S. Miller
2001-12-13 18:13 ` Gérard Roudier
2001-12-13 0:06 ` David S. Miller
2001-12-13 16:39 ` Gérard Roudier
2001-12-12 16:39 ` Gérard Roudier
2001-12-13 20:10 ` Steve Lord
2001-12-13 20:15 ` Justin T. Gibbs
2001-12-13 20:29 ` Steve Lord
2001-12-13 20:48 ` Justin T. Gibbs
2001-12-13 20:58 ` Steve Lord
2001-12-13 21:17 ` Steve Lord
2001-12-13 21:27 ` David S. Miller
2001-12-14 15:16 ` Jens Axboe
2001-12-14 16:15 ` Jens Axboe
2001-12-14 16:22 ` Alok K. Dhir
2001-12-14 16:32 ` Jens Axboe
2001-12-14 16:25 ` Stephen Lord
2001-12-14 16:24 ` Jens Axboe
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=20011212.162603.28785873.davem@redhat.com \
--to=davem@redhat.com \
--cc=LB33JM16@yahoo.com \
--cc=andrea@suse.de \
--cc=axboe@suse.de \
--cc=gibbs@scsiguy.com \
--cc=groudier@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox