From: Dagobert Michelsen <dam@opencsw.org>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: segaloco via TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Clever code
Date: Tue, 13 Dec 2022 10:45:21 +0100 [thread overview]
Message-ID: <7457C808-1BD0-4C21-A361-6E58D0F67783@opencsw.org> (raw)
In-Reply-To: <20221213080537.AF4E521911@orac.inputplus.co.uk>
Hi Ralph,
> Am 13.12.2022 um 09:05 schrieb Ralph Corderoy <ralph@inputplus.co.uk>:
>
> Hi George,
>
>> The "sticky" bit was quite clever. tell the OS to keep something
>> memory resident
>
> Was it ever more than a hint? I've not heard of it locking or pinning
> an executable to memory.
Funny thing is that it meant the opposite on Solaris: files with the
sticky bit set avoided the file to go through the page cache and therefore
would never be held in memory. This was e.g. set for swapfiles.
Obviously it is counterproductive to cache stuff in memory which is going
to be swapped out...
Best regards
— Dago
--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896
next prev parent reply other threads:[~2022-12-13 9:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 3:30 Rudi Blom
2022-12-13 3:41 ` Warner Losh
2022-12-13 3:53 ` Dave Horsfall
2022-12-13 4:03 ` George Michaelson
2022-12-13 8:05 ` Ralph Corderoy
2022-12-13 9:45 ` Dagobert Michelsen [this message]
2022-12-13 7:47 ` Ralph Corderoy
2022-12-13 19:56 ` Dave Horsfall
2022-12-13 11:46 ` John P. Linderman
2022-12-13 14:07 ` Douglas McIlroy
2022-12-13 14:31 ` arnold
2022-12-13 14:48 ` Ralph Corderoy
2022-12-13 15:10 ` Douglas McIlroy
2022-12-13 15:34 ` Stuff Received
2022-12-13 15:56 ` Ralph Corderoy
2022-12-13 23:02 ` Harald Arnesen
2022-12-14 7:31 ` arnold
2022-12-15 18:06 ` Marc Donner
2022-12-15 18:08 ` Marc Donner
2022-12-15 6:30 ` [TUHS] Delay line memory (was: Clever code) Greg 'groggy' Lehey
2022-12-13 15:52 ` [TUHS] Re: Clever code Bakul Shah
2022-12-13 16:14 ` Ralph Corderoy
2022-12-13 16:30 ` Bakul Shah
2022-12-15 6:39 ` [TUHS] Sector interleaving (was: Clever code) Greg 'groggy' Lehey
-- strict thread matches above, loose matches on Subject: below --
2022-12-13 18:02 [TUHS] Re: Clever code Noel Chiappa
2022-12-13 17:58 Noel Chiappa
2022-12-13 18:51 ` G. Branden Robinson
2022-12-13 20:14 ` segaloco via TUHS
2022-12-13 20:58 ` Warren Toomey via TUHS
2022-12-14 2:28 ` Luther Johnson
2022-12-11 20:03 [TUHS] Re: Stdin Redirect in Cu History/Alternatives? Larry McVoy
2022-12-12 2:15 ` [TUHS] Clever code (was " Bakul Shah
2022-12-12 9:48 ` [TUHS] Re: Clever code Michael Kjörling
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=7457C808-1BD0-4C21-A361-6E58D0F67783@opencsw.org \
--to=dam@opencsw.org \
--cc=ralph@inputplus.co.uk \
--cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).