From: David Miller <davem@davemloft.net>
To: cascardo@linux.vnet.ibm.com
Cc: venkat.x.venkatsubra@oracle.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, dledford@redhat.com,
Jes.Sorensen@redhat.com, rds-devel@oss.oracle.com
Subject: Re: [PATCH] rds_rdma: don't assume infiniband device is PCI
Date: Thu, 05 Jan 2012 13:57:51 -0500 (EST) [thread overview]
Message-ID: <20120105.135751.2230446777137893740.davem@davemloft.net> (raw)
In-Reply-To: <20120105170523.GA19022@oc1711230544.ibm.com>
From: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
Date: Thu, 5 Jan 2012 15:05:24 -0200
> On Thu, Jan 05, 2012 at 08:56:34AM -0800, Venkat Venkatsubra wrote:
>> Hi Cascardo,
>>
>> Your changes look good to me.
>> But our latest code doesn't use this rdsibdev_to_node macro anywhere.
>> Checking with the people in my group who know the history of the NUMA feature.
>> Trying to find out if the call to kzalloc_node() can be replaced by kzalloc().
>> In which case this macro can be removed.
>>
>> I will keep you posted.
>>
>> Venkat
>>
>
> Hi, Venkat.
>
> Do you have any public tree where we can track the last changes in RDS?
> Note that I have changed ibsdev_to_node, which rdsibdev_to_node makes
> use of. Anyway, replacing kzalloc_node with kzalloc has crossed my mind,
> but since I was not sure if this would affect latency of RDS in any use
> cases, I kept that and used a better function to get the node from the
> device. And we have dev_to_node since 2.6.20, so it should not be a
> problem to use it.
>
> If possible, keep everyone copied and avoid top posting.
Indeed, otherwise it's impossible for anyone to follow the progress on
this patch. If anything, you should never remove netdev from the CC:
list when discussing a patch. Otherwise the followups don't make into
our patch tracking system at:
http://patchwork.ozlabs.org/project/netdev/list/
next prev parent reply other threads:[~2012-01-05 18:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ed54708d-990e-4c8f-8057-50a70f93d3d8@default>
2012-01-05 17:05 ` [PATCH] rds_rdma: don't assume infiniband device is PCI Thadeu Lima de Souza Cascardo
2012-01-05 18:57 ` David Miller [this message]
2012-01-06 15:57 ` Thadeu Lima de Souza Cascardo
2012-01-06 17:43 ` Thadeu Lima de Souza Cascardo
2012-01-06 19:27 Venkat Venkatsubra
-- strict thread matches above, loose matches on Subject: below --
2012-01-04 22:03 Thadeu Lima de Souza Cascardo
2012-01-06 17:47 ` Roland Dreier
2012-01-06 17:49 ` Roland Dreier
2012-01-13 18:17 ` Thadeu Lima de Souza Cascardo
2012-01-13 18:25 ` David Miller
2012-01-13 18:52 ` Thadeu Lima de Souza Cascardo
2012-01-13 21:12 ` David Miller
2012-01-13 21:21 ` Thadeu Lima de Souza Cascardo
2012-01-13 18:35 ` Roland Dreier
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=20120105.135751.2230446777137893740.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Jes.Sorensen@redhat.com \
--cc=cascardo@linux.vnet.ibm.com \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=venkat.x.venkatsubra@oracle.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;
as well as URLs for NNTP newsgroup(s).