linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	Boaz Harrosh <bharrosh@panasas.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Douglas Gilbert <dgilbert@interlog.com>,
	Jesper Juhl <jj@chaosbits.net>
Subject: Re: [RFC-v4 07/12] iscsi-target: Add CHAP Authentication support using libcrypto
Date: Mon, 21 Mar 2011 20:05:42 -0500	[thread overview]
Message-ID: <4D87F5E6.3010208@cs.wisc.edu> (raw)
In-Reply-To: <1300613497-2091-8-git-send-email-nab@linux-iscsi.org>

On 03/20/2011 04:31 AM, Nicholas A. Bellinger wrote:
> +static struct iscsi_chap *chap_server_open(
> +	struct iscsi_conn *conn,
> +	struct iscsi_node_auth *auth,
> +	const char *A_str,
> +	char *AIC_str,
> +	unsigned int *AIC_len)

Lot of mixed cases like this and below in the patch.



> +
> +static int chap_server_compute_md5(
> +	struct iscsi_conn *conn,
> +	struct iscsi_node_auth *auth,
> +	char *NR_in_ptr,
> +	char *NR_out_ptr,
> +	unsigned int *NR_out_len)



> +	return 2;
> +}
> diff --git a/drivers/target/iscsi/iscsi_target_auth.h b/drivers/target/iscsi/iscsi_target_auth.h
> new file mode 100644
> index 0000000..17b042d
> --- /dev/null
> +++ b/drivers/target/iscsi/iscsi_target_auth.h



> +
> +struct iscsi_chap {
> +	unsigned char	digest_type;
> +	unsigned char	id;
> +	unsigned char	challenge[CHAP_CHALLENGE_LENGTH];
> +	unsigned int	challenge_len;
> +	unsigned int	authenticate_target;
> +	unsigned int	chap_state;
> +} ____cacheline_aligned;
> +

Why are almost all structs in the patches ____cacheline_aligned? Is it 
something we are just doing now, or does this affect performance somehow 
even though the struct is not used in a perf path?

  reply	other threads:[~2011-03-22  1:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-20  9:31 [RFC-v4 00/12] iSCSI target v4.1.0-rc1 series for .39-rc1 Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 01/12] iscsi: Resolve iscsi_proto.h naming conflicts with drivers/target/iscsi Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 02/12] iscsi-target: Add primary iSCSI request/response state machine logic Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 03/12] iscsi-target: Add TCM v4 compatiable ConfigFS control plane Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 04/12] iscsi-target: Add configfs fabric dependent statistics Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 05/12] iscsi-target: Add TPG and Device logic Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 06/12] iscsi-target: Add iSCSI Login Negotiation and Parameter logic Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 07/12] iscsi-target: Add CHAP Authentication support using libcrypto Nicholas A. Bellinger
2011-03-22  1:05   ` Mike Christie [this message]
2011-03-22  1:50     ` Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 08/12] iscsi-target: Add Sequence/PDU list + DataIN response logic Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 09/12] iscsi-target: Add iSCSI Error Recovery Hierarchy support Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 10/12] iscsi-target: Add support for task management operations Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 11/12] iscsi-target: Add misc utility and debug logic Nicholas A. Bellinger
2011-03-22  4:04   ` Mike Christie
2011-03-22  5:04     ` Mike Christie
2011-03-22 21:35     ` Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 12/12] iscsi-target: Add Makefile/Kconfig and update TCM top level Nicholas A. Bellinger
2011-03-21 20:54 ` [RFC-v4 00/12] iSCSI target v4.1.0-rc1 series for .39-rc1 Nicholas A. Bellinger
2011-03-21 21:07   ` James Bottomley
2011-03-21 21:06     ` Nicholas A. Bellinger
2011-03-21 21:15       ` James Bottomley
2011-03-21 21:18         ` 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=4D87F5E6.3010208@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=bharrosh@panasas.com \
    --cc=dgilbert@interlog.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jj@chaosbits.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=sfr@canb.auug.org.au \
    /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).