mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Patrick Gefre <pfg@sgi.com>
Cc: linux-kernel@vger.kernel.org, davidm@napali.hpl.hp.com, jbarnes@sgi.com
Subject: Re: [PATCH] Altix I/O code cleanup
Date: Mon, 13 Oct 2003 09:56:52 +0100	[thread overview]
Message-ID: <20031013095652.A25495@infradead.org> (raw)
In-Reply-To: <3F872984.7877D382@sgi.com>; from pfg@sgi.com on Fri, Oct 10, 2003 at 04:49:57PM -0500

On Fri, Oct 10, 2003 at 04:49:57PM -0500, Patrick Gefre wrote:
> This is my first patch for this - more to come ....

It would be nice to give those credits who submitted those patches.
And life would be a lot simpler if you wouldn't submit my individual
patches instead of putting them into a big one - this gives useful
entries in the revision history and allows for easier binary search
if something goes wrong.

p.s. the right list for this would probably be linux-ia64@vger.kernel.org

>  
>  void *
> -snia_kmem_zalloc(size_t size, int flag)
> +snia_kmem_zalloc(size_t size)
>  {
>          void *ptr = kmalloc(size, GFP_KERNEL);

passing a gfp_mask down here would make sense..

> - * the alloc/free_node routines do a simple kmalloc for now ..
> - */
> -void *
> -snia_kmem_alloc_node(register size_t size, register int flags, cnodeid_t node)
> -{
> -	/* someday will Allocate on node 'node' */
> -	return(kmalloc(size, GFP_KERNEL));
> -}
> -
> -void *
> -snia_kmem_zalloc_node(register size_t size, register int flags, cnodeid_t node)
> -{
> -	void *ptr = kmalloc(size, GFP_KERNEL);
> -	if ( ptr )
> -		BZERO(ptr, size);
> -        return(ptr);
> -}

Why do you remove the per-nod wrappers?  Unlike the other these actually
had some use as preparation for a node-aware kmalloc..

>  	int rc;
> -	extern void * snia_kmem_zalloc(size_t size, int flag);
> +	extern void * snia_kmem_zalloc(size_t size);

This is in a header, isn't it?

>  
> -	xvolinfo = snia_kmem_zalloc(sizeof(struct xswitch_vol_s), GFP_KERNEL);
> +	xvolinfo = snia_kmem_zalloc(sizeof(struct xswitch_vol_s));

You still need to handle a NULL return here.

>  
> -	intr_hdl = snia_kmem_alloc_node(sizeof(struct hub_intr_s), KM_NOSLEEP, cnode);
> +	intr_hdl = kmalloc(sizeof(struct hub_intr_s), GFP_KERNEL);
>  	ASSERT_ALWAYS(intr_hdl);

NULL return not handled again (and the assert is totally useless)

> -#define NEWAf(ptr,n,f)	(ptr = snia_kmem_zalloc((n)*sizeof (*(ptr)), (f&PCIIO_NOSLEEP)?KM_NOSLEEP:KM_SLEEP))
> -#define NEWA(ptr,n)	(ptr = snia_kmem_zalloc((n)*sizeof (*(ptr)), KM_SLEEP))
> +#define NEWAf(ptr,n,f)	(ptr = snia_kmem_zalloc((n)*sizeof (*(ptr))))
> +#define NEWA(ptr,n)	(ptr = snia_kmem_zalloc((n)*sizeof (*(ptr))))
>  #define DELA(ptr,n)	(kfree(ptr))

What about killing this stupid wrappers while you're at it?
 Also PCIIO_NOSLEEP is never set.


  parent reply	other threads:[~2003-10-13  8:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10 21:49 Patrick Gefre
2003-10-10 21:51 ` Jesse Barnes
2003-10-10 22:50   ` David Mosberger
2003-10-10 23:51     ` Jesse Barnes
2003-10-13  8:58     ` Christoph Hellwig
2003-10-13 10:55       ` Andrew Morton
2003-10-13 14:06         ` Christoph Hellwig
2003-10-13  8:56 ` Christoph Hellwig [this message]
2003-10-15  8:07   ` Jes Sorensen
2003-10-15 12:55     ` Christoph Hellwig
2003-10-16 13:08       ` Jes Sorensen
2003-10-16 16:40         ` Colin Ngam
2003-10-17  8:11           ` Christoph Hellwig
2003-10-17 13:36             ` Jes Sorensen

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=20031013095652.A25495@infradead.org \
    --to=hch@infradead.org \
    --cc=davidm@napali.hpl.hp.com \
    --cc=jbarnes@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pfg@sgi.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

Powered by JetHome