mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gábor Lénárt <lgb@vega.digitel2002.hu>
To: Thunder from the hill <thunder@ngforever.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: vfat <-> vfat copying of ~700MB file, so slow!
Date: Thu, 25 Jan 2001 21:28:25 +0100	[thread overview]
Message-ID: <20010125212825.B23684@vega.digitel2002.hu> (raw)
In-Reply-To: <20010124131431.A19957@ikar.t17.ds.pwr.wroc.pl> <997u6tsn18dp9u1h97q4j5jc9a2amn1nsp@i-vic.net> <20010124193525.A28379@ikar.t17.ds.pwr.wroc.pl> <3A7076E3.D9E6AF8B@ngforever.de>
In-Reply-To: <3A7076E3.D9E6AF8B@ngforever.de>; from thunder@ngforever.de on Thu, Jan 25, 2001 at 11:56:35AM -0700

On Thu, Jan 25, 2001 at 11:56:35AM -0700, Thunder from the hill wrote:
> 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.

Hmmm, imho this is a more general problem. Of course kernel does not know
if this is a single copy or data should be cached since it will be used
frequently in the near future. I don't know kernel internals very well
but I think cache is block cache. On higher layer (fs) it would be possible
to check out that we simply read blocks of file linear (which means
something like you mentioned especially on big files). I met similar
problems when I copy a harddisk to another (same type), with simple dd'ing
/dev/hda to /dev/hdb. Even with 192Mbs of RAM, the system goes down to
a very uninteractive state :( This copy task may be implemented on raw devices
to avoid caching nowdays. Please correct me, because these are only feelings
or what :)

-- 
 --[ Gábor Lénárt ]---[ Vivendi Telecom Hungary ]--[ lgb@supervisor.hu ]--
 U have 8 bit comp or chip of them and it's unused or to be sold? Call me!
 -------[ +36 30 2270823 ]------> LGB <-----[ Linux/UNIX/8bit 4ever ]-----
-
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 20:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-24 12:14 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
2001-01-25 20:28       ` Gábor Lénárt [this message]
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=20010125212825.B23684@vega.digitel2002.hu \
    --to=lgb@vega.digitel2002.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder@ngforever.de \
    /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

all inboxes | Powered by JetHome®