public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Olsson <mnemo@minimum.se>
To: linux-kernel@vger.kernel.org
Subject: Re: why swap at all? (what the user feels)
Date: Tue, 01 Jun 2004 19:38:54 +0200	[thread overview]
Message-ID: <40BCBF2E.7030802@minimum.se> (raw)
In-Reply-To: <20040601164946.GA22798@ncsu.edu>

Hi,

 From a pure *users* perspective the most evil part of my computer is 
the harddrive, because it has three bad properties;

-- its slowing stuff down
-- its very noisy
-- its sucks my battery dry (on laptops)

I dont care as much about how fast or efficient the swapping system 
really is, what does annoy me is when it lets me down. Say I do some 
action repeatedly every once in a while and it always takes about X 
milliseconds, when after a while that same action takes 2*X 
milliseconds. Now I'm DISAPPOINTED and I got a grudge with kswapd.

Its *emotionally* more 'okay' for the harddrive to its thing when I 
initiate it through some action (launching program, copying files) 
because then I expect it.

 From what I've read previously in this thread, it seems to me that the 
only major problem with swapping that not all users want file system 
cache to swap out actual applications (thus making that somewhat aged 
mozilla window abit laggy).

Maybe we could just have a "Allow file system cache to swap out 
applications checkbox somewhere"?

Or, Am I missing something?




Sincerly,
/m

jlnance@unity.ncsu.edu wrote:
> On Tue, Jun 01, 2004 at 02:57:00PM +0300, Lenar L?hmus wrote:
> 
>>jlnance@unity.ncsu.edu wrote:
>>
>>
>>>I'm not sure.  Copying a file is a pretty good indication that you
>>>are about to do something with either the new or the old file.
>>>
>>
>>Like taking the new file with me on USB dongle and deleting old one? 
>>Caching the file really doesn't help in this case.
> 
> 
> No, it does not help in this case.
> 
> Not putting things in cache is a solution for the problem of
> having useful stuff pushed out of the cache.  However, fixing
> the problem this way may create other problems if it causes
> us to fail to put useful things into the cache.
> 
> The point I was trying (perhaps unsuccessfully) to make, is
> that we should be careful about not caching things.  We are
> likely to break other corner cases by fixing the ones we
> are discussing.
> 
> Thanks,
> 
> Jim
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

  reply	other threads:[~2004-06-01 17:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.fegqf9v.kmidof@ifi.uio.no>
     [not found] ` <fa.bqpvcrs.u648jq@ifi.uio.no>
2004-05-27 11:39   ` why swap at all? Andy Lutomirski
2004-05-28 21:37     ` Denis Vlasenko
2004-05-28 22:28       ` Bernd Eckenfels
2004-05-29  7:31         ` Denis Vlasenko
2004-05-29  8:40           ` MM patches (was Re: why swap at all?) Nick Piggin
2004-05-29  8:46             ` Nick Piggin
     [not found]             ` <200405292014.23559.matt@lpbproductions.com>
2004-05-30  3:31               ` Nick Piggin
2004-05-31 13:13             ` Tvrtko A. Uršulin
2004-05-31 13:33               ` Con Kolivas
2004-05-31 17:34             ` Andy Lutomirski
2004-05-31 10:49         ` why swap at all? jlnance
2004-06-01 11:57           ` Lenar Lõhmus
2004-06-01 12:27             ` Robin Rosenberg
2004-06-01 16:49             ` jlnance
2004-06-01 17:38               ` Martin Olsson [this message]
2004-06-01 17:57                 ` why swap at all? (what the user feels) Valdis.Kletnieks
2004-06-01 18:01                 ` David Schwartz
2004-06-01 19:01                   ` Robin Rosenberg
2004-06-01 19:04                     ` David Schwartz
2004-06-02 18:38               ` why swap at all? John Hendrikx
2004-06-01 12:21           ` David B. Stevens

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=40BCBF2E.7030802@minimum.se \
    --to=mnemo@minimum.se \
    --cc=linux-kernel@vger.kernel.org \
    /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