public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thunder from the hill <thunder@ngforever.de>
To: Arkadiusz Miskiewicz <misiek@pld.ORG.PL>
Cc: linux-kernel@vger.kernel.org
Subject: Re: vfat <-> vfat copying of ~700MB file, so slow!
Date: Thu, 25 Jan 2001 11:56:35 -0700	[thread overview]
Message-ID: <3A7076E3.D9E6AF8B@ngforever.de> (raw)
In-Reply-To: <20010124131431.A19957@ikar.t17.ds.pwr.wroc.pl> <997u6tsn18dp9u1h97q4j5jc9a2amn1nsp@i-vic.net> <20010124193525.A28379@ikar.t17.ds.pwr.wroc.pl>

Arkadiusz Miskiewicz wrote:
> 
> On/Dnia Wed, Jan 24, 2001 at 12:23:03PM -0600, Brad Felmey wrote/napisa³(a)
> > > I/O support  =  0 (default 16-bit)
> >
> > hdparm -c1 /dev/hda, or are you running in 16-bit mode on purpose?
> no purpose. Setting this can only speed up all operations a bit but it doesn't
> change nothing in vfat <-> vfat copying. It still slows down while copying.
I noticed the kernel to increase cache and let the buffers break down during long file copies, it seems like this is the wrong way if only copying one large file. This also happens on SMB connections. I don't know if this info is useful.

Thunder
---
I did a "cat /boot/vmlinuz >> /dev/audio" - and I think I heard god...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-25 18:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-24 12:14 vfat <-> vfat copying of ~700MB file, so slow! Arkadiusz Miskiewicz
2001-01-24 18:23 ` Brad Felmey
2001-01-24 18:35   ` Arkadiusz Miskiewicz
2001-01-25 18:56     ` Thunder from the hill [this message]
2001-01-25 20:28       ` Gábor Lénárt
2001-01-24 21:50   ` Eric Lammerts
2001-01-24 20:53 ` Albert D. Cahalan
2001-01-26 17:41   ` Pavel Machek
2001-01-28  5:52     ` Ion Badulescu

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=3A7076E3.D9E6AF8B@ngforever.de \
    --to=thunder@ngforever.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=misiek@pld.ORG.PL \
    /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