From: Daniel Borkmann <dborkman@redhat.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-sctp@vger.kernel.org" <linux-sctp@vger.kernel.org>
Subject: Re: [PATCH net-next] loopback: sctp: add NETIF_F_SCTP_CSUM to device features
Date: Mon, 24 Feb 2014 13:36:03 +0000 [thread overview]
Message-ID: <530B4AC3.2040903@redhat.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D0F6C99F9@AcuExch.aculab.com>
On 02/24/2014 02:24 PM, David Laight wrote:
...
> Which architecture and which version of crc32_le() does your kernel use?
It's using slice-by-8 algorithm, and my machine is [only]
a core i7 (x86_64). Apparently, it is not using the crypto
version that is accelerated.
> (I'd guess there are several lurking).
> Whichever function you are using wants killing.
>
> David
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Borkmann <dborkman@redhat.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-sctp@vger.kernel.org" <linux-sctp@vger.kernel.org>
Subject: Re: [PATCH net-next] loopback: sctp: add NETIF_F_SCTP_CSUM to device features
Date: Mon, 24 Feb 2014 14:36:03 +0100 [thread overview]
Message-ID: <530B4AC3.2040903@redhat.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D0F6C99F9@AcuExch.aculab.com>
On 02/24/2014 02:24 PM, David Laight wrote:
...
> Which architecture and which version of crc32_le() does your kernel use?
It's using slice-by-8 algorithm, and my machine is [only]
a core i7 (x86_64). Apparently, it is not using the crypto
version that is accelerated.
> (I'd guess there are several lurking).
> Whichever function you are using wants killing.
>
> David
next prev parent reply other threads:[~2014-02-24 13:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 13:01 [PATCH net-next] loopback: sctp: add NETIF_F_SCTP_CSUM to device features Daniel Borkmann
2014-02-22 13:01 ` Daniel Borkmann
2014-02-24 10:17 ` David Laight
2014-02-24 10:31 ` Daniel Borkmann
2014-02-24 10:31 ` Daniel Borkmann
2014-02-24 10:42 ` David Laight
2014-02-24 12:02 ` Daniel Borkmann
2014-02-24 12:02 ` Daniel Borkmann
2014-02-24 13:24 ` David Laight
2014-02-24 13:36 ` Daniel Borkmann [this message]
2014-02-24 13:36 ` Daniel Borkmann
2014-02-24 14:07 ` David Laight
2014-02-24 14:07 ` David Laight
2014-02-24 14:06 ` Daniel Borkmann
2014-02-24 14:06 ` Daniel Borkmann
2014-02-24 14:28 ` David Laight
2014-02-25 0:00 ` David Miller
2014-02-25 0:00 ` David Miller
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=530B4AC3.2040903@redhat.com \
--to=dborkman@redhat.com \
--cc=David.Laight@ACULAB.COM \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.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.