All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang, Ziye <ziye.yang at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] CRC32 optimization for ARM platform
Date: Tue, 15 Jan 2019 07:24:55 +0000	[thread overview]
Message-ID: <FA6C2217B01E9D48A581BB48660210143E0B4EEC@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: 389f0c6d-8e9b-b64b-e35c-c7876d9c14aa@dev.mellanox.co.il

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

Hi Sasha,

Thanks for mentioning this patch.  PS: For NVMe-oF TCP, the default behavior is that the header digest and data digest is not enabled. But definitely, if you enabled, with accelerated CRC32 function, it would be helpful.




Best Regards
Ziye Yang 

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Sasha Kotchubievsky
Sent: Tuesday, January 15, 2019 3:18 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] CRC32 optimization for ARM platform

Hi,

Richael Zhuang from ARM submitted  CRC32 optimization for ARM:

https://review.gerrithub.io/c/spdk/spdk/+/437218

I tested  the patch and it significantly boosts NVME-OF TCP on ARM platform. Can we move forward with the patch and merge it into master?

Best regards

Sasha

_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk

             reply	other threads:[~2019-01-15  7:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15  7:24 Yang, Ziye [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-16 10:05 [SPDK] CRC32 optimization for ARM platform Sasha Kotchubievsky
2019-01-15 23:16 Harris, James R
2019-01-15  7:17 Sasha Kotchubievsky

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=FA6C2217B01E9D48A581BB48660210143E0B4EEC@shsmsx102.ccr.corp.intel.com \
    --to=spdk@lists.01.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 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.