DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] ZUC PMD as shared library
Date: Wed, 12 Oct 2016 09:22:38 +0200	[thread overview]
Message-ID: <1668805.iDXjnVEbkV@xps13> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8973CA07CC6@IRSMSX108.ger.corp.intel.com>

2016-10-12 02:23, De Lara Guarch, Pablo:
> Hi Thomas,
> 
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > 
> > Hi Pablo,
> > 
> > You are probably aware of the issue, but I would like to make it clear
> > in case someone else run into the same trouble:
> > 
> > It is impossible to build the ZUC crypto PMD as a shared library:
> > 
> > libsso-zuc-0.1.1/build/libsso_zuc.a(sso_zuc_yasm.o):
> > 	relocation R_X86_64_32 against `EK_d' can not be used
> > 	when making a shared object; recompile with -fPIC
> > 
> > The library libsso-zuc-0.1.1 needs an update to make the asm code
> > relocatable.
> > Should we explicit this limitation in the PMD doc?
> 
> Sorry for not replying to this earlier.
> Yes, you are right, thanks for pointing it out.
> I think the same problem is in KASUMI, so I will send a doc update for both PMDs.

No, KASUMI works as shared library, because there is no asm code.

Documenting the bug would be nice as a first step.
But it is a serious bug, so a fix in ZUC library is highly desirable.

  reply	other threads:[~2016-10-12  7:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-08 17:19 Thomas Monjalon
2016-10-12  2:23 ` De Lara Guarch, Pablo
2016-10-12  7:22   ` Thomas Monjalon [this message]
2016-10-13 18:30     ` De Lara Guarch, Pablo
2017-04-04 12:15 Thomas Monjalon
2017-04-05  9:46 ` De Lara Guarch, Pablo

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=1668805.iDXjnVEbkV@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.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).