mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Matthew Wilcox <willy@debian.org>
Cc: Linus Torvalds <torvalds@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] expand_resource
Date: Tue, 30 Sep 2003 22:27:08 +0100	[thread overview]
Message-ID: <20030930222708.A10154@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030930210410.GD24824@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Tue, Sep 30, 2003 at 10:04:10PM +0100

On Tue, Sep 30, 2003 at 10:04:10PM +0100, Matthew Wilcox wrote:
> Rewrite expand_resource() to be racefree and move it to kernel/resource.c.
> 
>...
> +/*
> + * Expand an existing resource by size amount.
> + */
> +int expand_resource(struct resource *res, unsigned long size,
> +			   unsigned long align)
> +{

Could we have the kerneldoc stuff added to this function?  My main
question though is - what is the intended purpose of "align" ?  As
it is implemented, it seems to have a weird behaviour:

- if we expand the "end" of the resource, we round it towards an
  address which is a multiple of align, but "start" may not be
  a multiple of align.
- if we expand "start", we round it down towards a multiple of
  align.  However, "end" may not be a multiple of align.

This may actually be of use to PCMCIA IO space handling - we only
have two windows, but we may need to expand them if we have a multi-
function card if we have more than 2 areas to map.  In this case,
we'd need to know whether "start" was expanded or "end" was expanded
since we can't change the use of the already-allocated resource.

It may make sense to do something more generic, like:

int adjust_resource(struct resource *res, unsigned long start,
		    unsigned long end);

so that the caller knows what he's requesting and knows whether that
change succeeded or failed.  However, it is something I'd need to
look deeper into when I have more time available to look at such
stuff, so please don't take the above as a well thought-out solution.

-- 
Russell King (rmk@arm.linux.org.uk)	http://www.arm.linux.org.uk/personal/
      Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
      maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                      2.6 Serial core

  reply	other threads:[~2003-09-30 21:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 21:04 Matthew Wilcox
2003-09-30 21:27 ` Russell King [this message]
2003-09-30 22:14   ` Matthew Wilcox
2003-09-30 22:33     ` Russell King
2003-10-01 14:25       ` Matthew Wilcox
2003-10-01 17:50         ` Matthias Urlichs

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=20030930222708.A10154@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=willy@debian.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

Powered by JetHome