From: Jes Sorensen <jes@trained-monkey.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Patrick Gefre <pfg@sgi.com>,
linux-kernel@vger.kernel.org, davidm@napali.hpl.hp.com,
jbarnes@sgi.com
Subject: Re: [PATCH] Altix I/O code cleanup
Date: 15 Oct 2003 04:07:07 -0400 [thread overview]
Message-ID: <yq0llrmncus.fsf@trained-monkey.org> (raw)
In-Reply-To: <20031013095652.A25495@infradead.org>
>>>>> "Christoph" == Christoph Hellwig <hch@infradead.org> writes:
Christoph> On Fri, Oct 10, 2003 at 04:49:57PM -0500, Patrick Gefre
Christoph> wrote:
Christoph> Why do you remove the per-nod wrappers? Unlike the other
Christoph> these actually had some use as preparation for a node-aware
Christoph> kmalloc..
I believe it was me who nuked it, until we start using it properly I
don't see any reason for keeping it as a placeholder.
>> - 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);
Christoph> NULL return not handled again (and the assert is totally
Christoph> useless)
ASSERT_ALWAYS checks it, it may not be pretty but it does check it.
>> -#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))
Christoph> What about killing this stupid wrappers while you're at it?
Christoph> Also PCIIO_NOSLEEP is never set.
All the NEWA stuff is going, I sent Pat a patch for it already, it's
going away.
Cheers,
Jes
next prev parent reply other threads:[~2003-10-15 8:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 21:49 [PATCH] Altix I/O code cleanup 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
2003-10-15 8:07 ` Jes Sorensen [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-10-13 15:22 Pat Gefre
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=yq0llrmncus.fsf@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=davidm@napali.hpl.hp.com \
--cc=hch@infradead.org \
--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 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.