From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Cc: Yevgeny Petrilin
<yevgenyp-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: mlx4 pci device table
Date: Wed, 23 Jun 2010 16:17:04 -0700 [thread overview]
Message-ID: <adafx0ds5jj.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1006221025130.11239-aDiYczhfhVLdX2U7gxhm1tBPR1lH4CV8@public.gmane.org> (Or Gerlitz's message of "Tue, 22 Jun 2010 10:30:17 +0300 (IDT)")
> If the table is placed in mlx4_core (as of today in upstream), then I
> assume the mlx4_en and _ib aren't being probed by pci hot-plug
> mechasnisms, correct? else if you put it in _en _ib et al files, then
> one has to maintain two copies of the table, but maybe this would be
> the correct approach? how this should work with multi-protcol mlx4
> devices and/or IBoE?
I think the current upstream location is correct. This matches the
practice of eg iw_cxgb3 as well as cxgb3i, bnx2i etc. This does have
the disadvantage that mlx4_en and mlx4_ib are not auto-loaded by PCI
hotplug, but so it goes.
--
Roland Dreier <rolandd-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org> || For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-23 23:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 7:30 mlx4 pci device table Or Gerlitz
[not found] ` <Pine.LNX.4.64.1006221025130.11239-aDiYczhfhVLdX2U7gxhm1tBPR1lH4CV8@public.gmane.org>
2010-06-23 23:17 ` Roland Dreier [this message]
[not found] ` <adafx0ds5jj.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-06-28 13:11 ` Or Gerlitz
[not found] ` <4C289F87.8050803-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2010-06-28 19:55 ` Tziporet Koren
[not found] ` <E113D394D7C5DB4F8FF691FA7EE9DB4439BA237127-WQlSmcKwN8Te+A/uUDamNg@public.gmane.org>
2010-06-28 20:26 ` Jason Gunthorpe
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=adafx0ds5jj.fsf@roland-alpha.cisco.com \
--to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org \
--cc=yevgenyp-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.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