All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matt W. Benjamin" <matt@cohortfs.com>
To: Somnath Roy <Somnath.Roy@sandisk.com>
Cc: ceph-devel@vger.kernel.org, Sage Weil <sage@newdream.net>,
	Ken Dreyer <kdreyer@redhat.com>
Subject: Re: xio messenger is not building by default
Date: Mon, 16 Mar 2015 14:22:04 -0400 (EDT)	[thread overview]
Message-ID: <1231373626.55.1426530124905.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <755F6B91B3BE364F9BCA11EA3F9E0C6F28CA3E46@SACMBXIP01.sdcorp.global.sandisk.com>

Hi,

----- "Somnath Roy" <Somnath.Roy@sandisk.com> wrote:

> I think installing the MLNX_OFED driver package will install most of
> the stuff(including libibverbs-dev). We need the following extra
> packages for building accelio.
> numactl libnuma-dev

Ah, that's also true.

> 
> But, what if user is building it without OFED driver package installed
> ?

Should it be possible?  I mean, to both build Xio and not have the header interface?

> BTW, I saw accelio was giving assert if I manually install
> libibverbs-dev from Ubuntu repo and upgrade this OFED driver later.
> Cleaning the repo and rebuilding solved the issue. Seems it was
> linking wrong libraries.

I think I've seen this.

> 
> Thanks & Regards
> Somnath
> 
> 
> -----Original Message-----
> From: Matt W. Benjamin [mailto:matt@cohortfs.com]
> Sent: Monday, March 16, 2015 9:34 AM
> To: Ken Dreyer
> Cc: ceph-devel@vger.kernel.org; Sage Weil; Somnath Roy
> Subject: Re: xio messenger is not building by default
> 
> Hi,
> 
> Yes, agree.  We do depend on librdmacm!
> 
> Matt
> 
> ----- "Ken Dreyer" <kdreyer@redhat.com> wrote:
> 
> > On 03/16/2015 10:20 AM, Matt W. Benjamin wrote:
> > > Hi,
> > >
> > > Arent OFED dependencies already packaged?  I assumed that only
> > Accelio would
> > > be a submodule.
> > >
> >
> > Thanks for pointing that out. It's in Fedora as libibverbs-devel,
> and
> > it's in Debian as libibverbs-dev. So you're right, Accelio is the
> only
> > one to be packaged.
> >
> > Looking at configure.ac, does README.xio need to be updated to
> mention
> > librdmacm?
> >
> > - Ken
> 
> --
> Matt Benjamin
> CohortFS, LLC.
> 315 West Huron Street, Suite 140A
> Ann Arbor, Michigan 48103
> 
> http://cohortfs.com
> 
> tel.  734-761-4689
> fax.  734-769-8938
> cel.  734-216-5309
> 
> ________________________________
> 
> PLEASE NOTE: The information contained in this electronic mail message
> is intended only for the use of the designated recipient(s) named
> above. If the reader of this message is not the intended recipient,
> you are hereby notified that you have received this message in error
> and that any review, dissemination, distribution, or copying of this
> message is strictly prohibited. If you have received this
> communication in error, please notify the sender by telephone or
> e-mail (as shown above) immediately and destroy any and all copies of
> this message in your possession (whether hard copies or electronically
> stored copies).

-- 
Matt Benjamin
CohortFS, LLC.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103

http://cohortfs.com

tel.  734-761-4689 
fax.  734-769-8938 
cel.  734-216-5309 

  reply	other threads:[~2015-03-16 18:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 23:35 xio messenger is not building by default Somnath Roy
2015-03-13 23:44 ` Sage Weil
2015-03-13 23:53   ` Somnath Roy
2015-03-14  0:40     ` Matt W. Benjamin
2015-03-16 14:17   ` Ken Dreyer
2015-03-16 16:20     ` Matt W. Benjamin
2015-03-16 16:31       ` Ken Dreyer
2015-03-16 16:33         ` Matt W. Benjamin
2015-03-16 17:27           ` Somnath Roy
2015-03-16 18:22             ` Matt W. Benjamin [this message]
2015-03-16 18:25               ` Somnath Roy
2015-03-16 18:29                 ` Matt W. Benjamin
2015-03-16 18:50                   ` Somnath Roy
2015-03-16 18:50                 ` Vu Pham
2015-03-16 18:58                   ` Somnath Roy
2015-03-16 19:09                     ` Vu Pham

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=1231373626.55.1426530124905.JavaMail.root@thunderbeast.private.linuxbox.com \
    --to=matt@cohortfs.com \
    --cc=Somnath.Roy@sandisk.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=kdreyer@redhat.com \
    --cc=sage@newdream.net \
    /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.