Hey guys!
I'm running 3.7 and am getting really, really crappy usb throughput :( -
# dd if=/dev/sd0c of=/dev/null bs=819200 count=100
100+0 records in
100+0 records out
8192 bytes transferred in 175.970 secs (465533 bytes/sec)
Here's an excerpt from my dmesg -
uhci0 at pci0 dev 29 functio
ect removable
sd0: 2000MB, 2000 cyl, 64 head, 32 sec, 512 bytes/sec, 4096000 sec total
dkcsum: wd0 matched BIOS disk 80
dkcsum: sd0 matched BIOS disk 81
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
On Tue, Oct 11, 2005 at 12:20:45PM -0400, Andrew Atrens wrote:
Hey guys!
I'm runni
Just for fun I ran 'top' during the said slow transfer, and it says -
load averages: 0.55, 0.20, 0.12
11:41:59
22 processes: 21 idle, 1 on processor
CPU states: 0.2% user, 0.0% nice, 0.2% system, 0.8% interrupt, 98.9% idle
Memory: Real: 8932K/100
Okay, I've upgraded to a kernel with tag=OPENBSD_3_7 which looks to be
the -stable or 'patch' tag, and while the situation has improved, performance
is still off by a factor of 5.
(I added the wd test below because with the 3.7 kernel it (interestingly)
matched
that of the flash stick. Now w
Hmmm.
I just ripped apm0 out of my kernel config and wd transfers improved. A lot!
-- [EMAIL PROTECTED]: ~ (17:39) --
# dd if=/dev/wd0c of=/dev/null bs=819200 count=20
20+0 records in
20+0 records out
16384000 bytes transferred in 0.711 secs (23012820 bytes/sec)
recall the old speed with apm0:
Michael Shalayeff wrote:
Making, drinking tea and reading an opus magnum from Andrew Atrens:
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
Okay, I've upgraded to a kernel with tag=OPENBSD_3_7 which looks to be
the -stable or 'patch' tag, and while the situati
I don't see the 'EHCI' controller in there anywhere. :(
UHCI == usb1.1
EHCI == usb2.0
Top speed for usb1.1 is roughly 1MB/s. Your getting that. :|
Two possibilities - your mobo doesn't do usb2.0 - or the ehci
device probe isn't grokking your hardware.
Andrew.
Jeff Ross wrote:
I've got a USB
Andreas Bihlmaier wrote:
-- [EMAIL PROTECTED]: ~ (17:39) --
# dd if=/dev/wd0c of=/dev/null bs=819200 count=20
20+0 records in
20+0 records out
16384000 bytes transferred in 0.711 secs (23012820 bytes/sec)
recall the old speed with apm0: -
-- [EMAIL PROTECTED]: ~ (17:13) --
# dd if=/dev/wd0c of
Hi Folks,
I'm running 3.7-stable and am trying to 'group' a compression
association with an esp association like so -
Not sure what these 'errno 209's are about either :('
# ipsecadm show
sadb_dump: satype ipcomp vers 2 len 14 seq 0 pid 0
errno 209: Unknown error: 209
sa: cpi 0x
Even though the card is detected, I'm not seeing any boost in
IPsec performance.
I'm getting 10Mb/s using 3des. The raw speed (no ipsec) of the
link is around 25Mb/s. This measured with netstrain.
Here's what dmesg says -
hifn0 at pci0 dev 13 function 0 "Hifn 7955/7954" rev 0x00: LZS 3DES ARC4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Folks,
Looking for a simple way to tag bittorent connections based on packet content
so that I can shape
them with pf/altq...
Heard it can be done with a combination of pf and snort .. googled some old
references to a
now-defunct freshmeat proj
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks,
I'm working on a embedded project and have been cycling through some
tradeoffs wrt using cf cards as disks.
I know these devices support wear-leveling, but I'm not sure how this
could work w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Hall wrote:
> Andrew Atrens wrote:
>
>> ...
>> And finally one last question that applies to both FFS and LFS - file
>> access/creation/modification metadata updates. Specifically I'm thinking
>> of atim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Folks,
I've got an ADSL connection and for the past few months
have been working out an ALTQ (well pf.conf) config to
allow me to manage my upstream b/w. Sometimes the behaviour
I'm seeing doesn't jibe with how I'd expect it to work and
I'm wonde
14 matches
Mail list logo
