From: "J.E.J. Bottomley" <James.Bottomley@steeleye.com>
To: Arnd Bergmann <ibm.com@arndb.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Scsi <linux-scsi@vger.kernel.org>
Subject: Re: [RFC][PATCH] move dma_mask into struct device
Date: Sat, 16 Nov 2002 12:01:59 -0500 [thread overview]
Message-ID: <200211161701.gAGH1xF03711@localhost.localdomain> (raw)
In-Reply-To: Message from Arnd Bergmann <arndb@de.ibm.com> of "Sat, 16 Nov 2002 19:26:52 +0100." <200211161926.52092.arndb@de.ibm.com>
arndb@de.ibm.com said:
> On my s390 system, I can have many thousand devices and none of them
> is doing DMA, so I would indeed call it architecture specific. Note
> that even in a normal PC system, most devices (e.g. CPUs, input
> devices or the disks attached to the host adapter) don't have any
> concept of DMA.
DMA itself is pervasive to almost every architecture, that's why we have the
DMA API. That some devices don't do DMA, I agree with (the struct scsi_device
is another example). However, in order to divorce DMA from the PCI bus, it
has to be obtainable from the generic device, without requiring knowledge of
the bus. In OO terms, it would be in a dmaable_device which inherits from
device, but for expediency in layering all this into the kernel means I'd have
to break almost every driver and introduce them to the concept of
dmaable_device, so it's just easier to expand device by a pointer.
James
next prev parent reply other threads:[~2002-11-16 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <arndb@de.ibm.com>
2002-11-16 17:23 ` [RFC][PATCH] move dma_mask into struct device Arnd Bergmann
2002-11-16 15:33 ` J.E.J. Bottomley
2002-11-16 18:26 ` Arnd Bergmann
2002-11-16 17:01 ` J.E.J. Bottomley [this message]
2002-11-16 19:56 ` Arnd Bergmann
2002-11-16 18:12 ` J.E.J. Bottomley
2002-11-16 20:46 ` Arnd Bergmann
2002-11-15 20:34 J.E.J. Bottomley
2002-11-16 0:19 ` Mike Anderson
2002-11-16 14:48 ` J.E.J. Bottomley
2002-11-16 20:33 ` Patrick Mansfield
2002-11-17 15:07 ` J.E.J. Bottomley
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=200211161701.gAGH1xF03711@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=ibm.com@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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