From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 5/5] scsi_debug: Implement support for DIF Type 2
Date: Thu, 27 Aug 2009 17:20:26 +0300 [thread overview]
Message-ID: <4A96962A.8050208@panasas.com> (raw)
In-Reply-To: <1251380478.6426.11.camel@mulgrave.site>
On 08/27/2009 04:41 PM, James Bottomley wrote:
>
> The general rule is not to confuse coding styles, so the correct way to
> add stuff is to use the existing conventions in the file. You can
> optionally convert the entire style if necessary. However, for these
> get_cpu_be macros, there's no real benefit other than saving typing, so
> a global conversion effort simply isn't worth it.
>
This is not right. The get_cpu_be macros are ten fold faster and smaller
on all the platforms we ever use. I'm talking about 16-96 to 1 for a 64 bit
operation.
Not to mention the heart attack it gives me every time. Is that index go down
or up? the shifts go bigger or smaller? even just for that I would wrap them,
triple check, and never use anything else. But the stronger fact of the matter
is that I don't think there is a single used ARCH that does shifts anymore.
> James
>
>
Boaz
next prev parent reply other threads:[~2009-08-27 14:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 6:17 DIF/DIX updates for 2.6.32 Martin K. Petersen
2009-08-26 6:17 ` [PATCH 1/5] SCSI: Add support for 32-byte CDBs Martin K. Petersen
2009-08-26 12:16 ` Boaz Harrosh
2009-08-27 6:38 ` Martin K. Petersen
2009-08-26 6:17 ` [PATCH 2/5] SCSI: Deprecate SCSI_PROT_*_CONVERT operations Martin K. Petersen
2009-08-26 6:17 ` [PATCH 3/5] sd: Detach DIF from block integrity infrastructure Martin K. Petersen
2009-08-26 6:18 ` [PATCH 4/5] sd: Support disks formatted with DIF Type 2 Martin K. Petersen
2009-08-26 12:26 ` Boaz Harrosh
2009-08-27 6:41 ` Martin K. Petersen
2009-08-26 6:18 ` [PATCH 5/5] scsi_debug: Implement support for " Martin K. Petersen
2009-08-26 12:40 ` Boaz Harrosh
2009-08-27 6:58 ` Martin K. Petersen
2009-08-27 9:35 ` Boaz Harrosh
2009-08-27 13:41 ` James Bottomley
2009-08-27 14:20 ` Boaz Harrosh [this message]
2009-08-27 14:30 ` James Bottomley
2009-08-27 14:47 ` Boaz Harrosh
2009-08-27 14:54 ` James Bottomley
2009-08-27 15:17 ` Douglas Gilbert
2009-08-27 15:39 ` Boaz Harrosh
2009-08-26 11:54 ` DIF/DIX updates for 2.6.32 Boaz Harrosh
2009-08-27 6:34 ` Martin K. Petersen
2009-08-27 9:49 ` Boaz Harrosh
2009-08-27 13:46 ` James Bottomley
2009-08-27 14:40 ` Boaz Harrosh
2009-08-27 14:51 ` James Bottomley
2009-08-27 15:18 ` Boaz Harrosh
2009-08-27 15:22 ` James Bottomley
2009-08-27 20:02 ` Martin K. Petersen
2009-08-27 20:05 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2009-09-04 8:36 Martin K. Petersen
2009-09-04 8:36 ` [PATCH 5/5] scsi_debug: Implement support for DIF Type 2 Martin K. Petersen
2009-09-11 19:20 DIF/DIX updates for 2.6.32 Martin K. Petersen
2009-09-11 19:20 ` [PATCH 5/5] scsi_debug: Implement support for DIF Type 2 Martin K. Petersen
2009-09-11 23:06 ` Douglas Gilbert
2009-09-18 21:32 Final DIF/DIX patches for 2.6.32 Martin K. Petersen
2009-09-18 21:33 ` [PATCH 5/5] scsi_debug: Implement support for DIF Type 2 Martin K. Petersen
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=4A96962A.8050208@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 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.