public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jesse.barnes@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 4/4] ia64 SPARSEMEM - SPARSEMEM code changes
Date: Mon, 23 May 2005 18:08:28 +0000	[thread overview]
Message-ID: <200505231108.28523.jesse.barnes@intel.com> (raw)
In-Reply-To: <20050523175117.GG2783@localhost.localdomain>

On Monday, May 23, 2005 10:51 am, Bob Picco wrote:
> +#ifdef	CONFIG_SPARSEMEM
> +/**
> + * register_sparse_mem - notify SPARSEMEM that this memory range
> exists. + * @start: physical start of range
> + * @end: physical end of range
> + * @arg: unused
> + *
> + */

No comment for the function (I guess it's pretty simple...).

> +static int __init register_sparse_mem(unsigned long start, unsigned
> long end, +	void *arg)
> +{
> +	int nid;
> +
> +	start = __pa(start) >> PAGE_SHIFT;
> +	end = __pa(end) >> PAGE_SHIFT;
> +	nid = early_pfn_to_nid(start);
> +	(void) memory_present(nid, start, end);

Is the (void) cast necessary?

> +#ifdef	CONFIG_SPARSEMEM
> +	efi_memmap_walk(register_sparse_mem, (void *) 0);
> +#endif

NULL here instead?

> -#ifndef CONFIG_DISCONTIGMEM
> +#ifndef	CONFIG_NEED_MULTIPLE_NODES

Just use a space instead of a tab I think.

> +#if	defined(CONFIG_SPARSEMEM) && defined(CONFIG_NUMA)

Ditto.

> +/*
> + * Because of holes evaluate on section limits.
> + */

A better comment block here maybe describing return values and such?

> +int early_pfn_to_nid(unsigned long pfn)
> +{
> +	int i, section = pfn >> PFN_SECTION_SHIFT, ssec, esec;
> +
> +	for (i = 0; i < num_node_memblks; i++) {
> +		ssec = node_memblk[i].start_paddr >> PA_SECTION_SHIFT;
> +		esec = (node_memblk[i].start_paddr + node_memblk[i].size +
> +			((1L << PA_SECTION_SHIFT) - 1)) >> PA_SECTION_SHIFT;
> +		if (section >= ssec && section < esec)
> +			break;
> +	}
> +
> +	if (i = num_node_memblks)
> +		return 0;
> +	else
> +		return node_memblk[i].nid;

You could just drop the else here if you wanted, maybe along with a 
comment by the return 0 saying that the pfn wasn't found?  Or you could 
turn the 'break' above into return node_memblk[i].nid and make the 
function return 0 unconditionally if the for loop exited.

So other than that cosmetic stuff, this patch looks ok.

Jesse

  reply	other threads:[~2005-05-23 18:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 17:51 [patch 4/4] ia64 SPARSEMEM - SPARSEMEM code changes Bob Picco
2005-05-23 18:08 ` Jesse Barnes [this message]
2005-05-23 21:20 ` Bob Picco

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=200505231108.28523.jesse.barnes@intel.com \
    --to=jesse.barnes@intel.com \
    --cc=linux-ia64@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