From: Matthew Wilcox <willy@debian.org>
To: Ryan Bradetich <rbradetich@uswest.net>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [PATCH] Additional Address cleanup
Date: Fri, 21 Sep 2001 19:35:56 +0100 [thread overview]
Message-ID: <20010921193556.A2765@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20010921104838.A2049@beavis.ybsoft.com>; from rbradetich@uswest.net on Fri, Sep 21, 2001 at 10:48:38AM -0600
On Fri, Sep 21, 2001 at 10:48:38AM -0600, Ryan Bradetich wrote:
> The simplification I made was to remove the HPA from index
> 0 of the addr[] in the parisc_device. I feel this is redundant
> since the device already records the HPA with the hpa field.
> By not including the HPA, it also saves a kmalloc on every
> parisc device to store the HPA, and an additional kfree/kmalloc
> when the device actually has additional addresses to store.
I haven't had time to review the patch, but I think it's an excellent
idea to remove the duplicate hpa and addr[0] entries. I was thinking
about doing it myself, but hadn't got round to checking it could be done.
I was also thinking about removing the `hpa' entry completely and using
struct resource to track the area claimed by the device. I think we
want to do this in any case for the card-mode dino support. This is a
later step, I think, so don't let this consideration slow you down.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2001-09-21 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 16:48 [parisc-linux] [PATCH] Additional Address cleanup Ryan Bradetich
2001-09-21 18:21 ` Ryan Bradetich
2001-09-21 18:35 ` Matthew Wilcox [this message]
2001-09-24 11:06 ` Rüdiger Scholz
2001-09-25 3:59 ` Ryan Bradetich
2001-09-25 17:33 ` Rüdiger Scholz
2001-09-25 19:00 ` Thomas Bogendoerfer
2001-10-01 17:12 ` Rüdiger Scholz
2001-10-02 12:57 ` Thomas Bogendoerfer
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=20010921193556.A2765@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rbradetich@uswest.net \
/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.