From: Andre Noll <maan@systemlinux.org>
To: Neil Brown <neilb@suse.de>
Cc: Raz <raziebe@gmail.com>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: raid0 hashing funtion
Date: Wed, 13 May 2009 15:18:54 +0200 [thread overview]
Message-ID: <20090513131854.GE11504@skl-net.de> (raw)
In-Reply-To: <18953.62556.265428.572219@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
On 08:12, Neil Brown wrote:
> On reflection, I am not convinced that the hash really does add value.
> You cannot have more entries in the list than there are drives, and
> you usually have much fewer. Given that consecutive entries in the
> list are likely to be in the same cache line, and the hash_table is in
> a totally different page, probing 3 or 4 locations in the list is
> probably faster than doing a lookup in the hash table. And as we
> would be able to get rid of that sector_div, we would probably get
> even more saving.
Yup, that's exactly what I was thinking when I looked at the code.
> The only cost would be if someone had a raid0 with lots of devices all
> of very different sizes. I suspect that case does not need to be
> optimised for. So I would probably be happy to accept a patch which
> removed that hash table.
I'll see if I can come up with a patch that gets rid of the hash table
and that one sector_div. Killing all instances of sector_div in raid0,
while possible and probably desirable, would be more involved though.
Thanks
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2009-05-13 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 13:29 raid0 hashing funtion Raz
2009-05-12 22:12 ` Neil Brown
2009-05-13 13:18 ` Andre Noll [this message]
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=20090513131854.GE11504@skl-net.de \
--to=maan@systemlinux.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=raziebe@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox