public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: linux-usb-devel@lists.sourceforge.net
Cc: Manfred Spraul <manfred@colorfullife.com>,
	David Brownell <david-b@pacbell.net>,
	Russell King <rmk@arm.linux.org.uk>,
	zaitcev@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: SLAB vs. pci_alloc_xxx in usb-uhci patch [RFC: API]
Date: Fri, 9 Mar 2001 13:35:03 -0500	[thread overview]
Message-ID: <20010309133502.R31345@sventech.com> (raw)
In-Reply-To: <001f01c0a5c0$e942d8f0$5517fea9@local> <00d401c0a5c6$f289d200$6800000a@brownell.org> <20010305232053.A16634@flint.arm.linux.org.uk> <15012.27969.175306.527274@pizda.ninka.net> <055e01c0a8b4$8d91dbe0$6800000a@brownell.org> <3AA91B2C.BEB85D8C@colorfullife.com> <15017.7950.106874.276894@pizda.ninka.net>
In-Reply-To: <15017.7950.106874.276894@pizda.ninka.net>; from David S. Miller on Fri, Mar 09, 2001 at 10:21:02AM -0800

On Fri, Mar 09, 2001, David S. Miller <davem@redhat.com> wrote:
> Manfred Spraul writes:
>  > Do lots of drivers need the reverse mapping? It wasn't on my todo list
>  > yet.
> 
> I am against any API which provides this.  It can be extremely
> expensive to do this on some architectures, and since the rest
> of the PCI dma API does not provide such an interface neither
> should the pool routines.

The API I hacked together for uhci.c didn't have this.

> Drivers can keep track of this kind of information themselves,
> and that is what I tell every driver author to do who complains
> of a lack of a "bus_to_virt()" type thing, it's just lazy
> programming.

Once I worked around not having a "bus_to_virt()" type thing I was happier
with the resulting code. I completely agree.

JE


  reply	other threads:[~2001-03-09 18:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-05 22:08 SLAB vs. pci_alloc_xxx in usb-uhci patch Manfred Spraul
2001-03-05 22:52 ` David Brownell
2001-03-05 23:20   ` Russell King
2001-03-06  2:09     ` Alan Cox
2001-03-06  2:29       ` [linux-usb-devel] " David Brownell
2001-03-06  4:53     ` David S. Miller
2001-03-09 16:18       ` SLAB vs. pci_alloc_xxx in usb-uhci patch [RFC: API] David Brownell
     [not found]         ` <3AA91B2C.BEB85D8C@colorfullife.com>
2001-03-09 18:21           ` David S. Miller
2001-03-09 18:35             ` Johannes Erdfelt [this message]
2001-03-09 19:42               ` [linux-usb-devel] " David Brownell
2001-03-09 20:07                 ` David S. Miller
2001-03-09 21:14                   ` David Brownell
2001-03-09 22:34                     ` Pete Zaitcev
2001-03-09 18:35             ` Alan Cox
2001-03-09 18:29           ` David Brownell
2001-03-09 19:14             ` Pete Zaitcev
2001-03-09 19:37               ` David Brownell
2001-03-09 19:04                 ` Gérard Roudier
2001-03-09 22:42                   ` David Brownell
2001-03-09 21:07                     ` Gérard Roudier
2001-03-10  3:11                       ` David Brownell
2001-03-09 20:00               ` David S. Miller
2001-03-09 21:38               ` [linux-usb-devel] " Alan Cox
2001-03-09 20:07             ` David S. Miller

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=20010309133502.R31345@sventech.com \
    --to=johannes@erdfelt.com \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=manfred@colorfullife.com \
    --cc=rmk@arm.linux.org.uk \
    --cc=zaitcev@redhat.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