linux-kernel - Re: PATA-disk named sda

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070706161950.32fc3139@the-village.bc.nu>
Date:	Fri, 6 Jul 2007 16:19:50 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Christoph Pleger <Christoph.Pleger@...uni-dortmund.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: PATA-disk named sda

> So, the name of the drive can depend on something which happens in the
> ramdisk environment. Does anybody know what that is? And is there a
> kernel command line parameter which restores the old behaviour?

Old IDE -> /dev/hd*
LibATA -> /dev/sd*

so if you build both sets of modules it depends who gets loaded first.

> And what about hdparm (setting 32bit I/O and multi-sector mode)? Suren
> wrote that 32bit I/O makes no sense when using DMA. Maybe that's right,
> but it does not correspond with my experiences. At least, I have the
> "feeling" that my IDE disks work much faster since I enabled 32bit
> support (DMA already was on before).

32bit I/O and multi-sector I/O are PIO specific features - they have no
effect on DMA performance. 32bit is on my todo list but very low priority
as for most systems it makes almost no difference.

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/