From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Ira Weiny <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Boris Chiu <boris.chiu-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] libibmad: To reserve upper 8 bits of tid used by solaris SRIOV driver
Date: Wed, 20 Mar 2013 16:33:22 -0600 [thread overview]
Message-ID: <20130320223322.GB30100@obsidianresearch.com> (raw)
In-Reply-To: <CAMLCd9LOuajya0_s4NhuUD4hUtHnc_NLi8sELnsEprash6t5Eg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, Mar 20, 2013 at 03:11:51PM -0700, Ira Weiny wrote:
> Why does this need to be done in user space? This seems like
> something which should be done in the kernel for all Transaction ID's
> which might be sent to the umad layer.
Agreed, if Solaris is going to emulate the Linux umad dev FD it should
be done properly. The kernel overrides some bits and returns the TRID
it actually put on the wire after the MAD is sent.
Linux is already doing this to add per-process uniqueness, per-guest
SRIOV uniqueness should use the same mechanism.
Thus, this masking is either redundant, or hiding a kernel bug..
Jason
--
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:[~2013-03-20 22:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 19:35 [PATCH] libibmad: To reserve upper 8 bits of tid used by solaris SRIOV driver Boris Chiu
[not found] ` <513F8386.5070208-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-03-20 22:11 ` Ira Weiny
[not found] ` <CAMLCd9LOuajya0_s4NhuUD4hUtHnc_NLi8sELnsEprash6t5Eg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-20 22:33 ` Jason Gunthorpe [this message]
[not found] ` <514A3996.601@oracle.com>
[not found] ` <514A3996.601-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-03-21 0:20 ` Fwd: " brendan doyle
[not found] ` <514A525F.7030706-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-03-21 0:51 ` Weiny, Ira
[not found] ` <2807E5FD2F6FDA4886F6618EAC48510EBB428F-8k97q/ur5Z1cIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-03-21 1:23 ` brendan doyle
2013-03-21 5:07 ` Jason Gunthorpe
[not found] ` <20130321050709.GA20882-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2013-03-21 18:14 ` brendan doyle
[not found] ` <514B4E17.5020703-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-03-21 18:45 ` Jason Gunthorpe
[not found] ` <20130321184507.GB8044-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2013-03-21 20:40 ` brendan doyle
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=20130320223322.GB30100@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=boris.chiu-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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