From: Herbert Xu <herbert@gondor.apana.org.au>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: James.Bottomley@hansenpartnership.com, hch@infradead.org,
rdunlap@xenotime.net, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [RFC 12/12] iscsi-target: Add Makefile/Kconfig and update TCM top level
Date: Tue, 8 Mar 2011 17:33:34 +0800 [thread overview]
Message-ID: <20110308093334.GA21996@gondor.apana.org.au> (raw)
In-Reply-To: <1299539747.19683.333.camel@haakon2.linux-iscsi.org>
Nicholas A. Bellinger <nab@linux-iscsi.org> wrote:
>
>> > I should mention this is with the following .config:
>> >
>> > CONFIG_CRYPTO_CRC32C=y
>> > CONFIG_CRYPTO_CRC32C_INTEL=m
This is why you get the unoptimised version. Had you selected
both as built-in or both as modules, then it would have worked
as intended.
> What about the following to simply call request_module("crc32c_intel")
> at module_init() time and top the extra iscsi_login_setup_crypto()
> code..?
If we're going to do this we should do it in the crypto layer,
and not litter every single crypto API user with such crap.
Currently we don't invoke request_module unless no implementation
is reigstered for an algorithm. You can change this so that it
also invokes request_module if we have not yet done so at least
once for that algorithm.
Patches are welcome.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2011-03-08 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1299036841-23677-1-git-send-email-nab@linux-iscsi.org>
[not found] ` <1299036841-23677-13-git-send-email-nab@linux-iscsi.org>
[not found] ` <20110301223251.11c95eed.rdunlap@xenotime.net>
[not found] ` <1299101531.5401.313.camel@haakon2.linux-iscsi.org>
2011-03-03 14:19 ` [RFC 12/12] iscsi-target: Add Makefile/Kconfig and update TCM top level Christoph Hellwig
2011-03-03 20:58 ` Nicholas A. Bellinger
2011-03-04 17:00 ` James Bottomley
2011-03-07 23:15 ` Nicholas A. Bellinger
2011-03-08 9:33 ` Herbert Xu [this message]
2011-03-10 8:02 ` Nicholas A. Bellinger
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=20110308093334.GA21996@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=James.Bottomley@hansenpartnership.com \
--cc=hch@infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=rdunlap@xenotime.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox