9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Kenji Arisawa <arisawa@ar.aichi-u.ac.jp>
To: 9front@9front.org
Subject: Re: [9front] cwfs fsmempercent
Date: Wed, 30 Apr 2014 23:41:40 +0900	[thread overview]
Message-ID: <CA794870-DE36-4C2B-85D9-F4C6C4F1385F@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <edd12afe17b1d29d9dfa30cc39d59228@felloff.net>

thanks. I will try and report.
by the way, I cannot compile pc64

term% pwd
/sys/src/9/pc64
term% mk
mk: ambiguous recipes for devusb.6:
	devusb.6 <-(mkfile:94)- ../pc/devusb.c
	devusb.6 <-(../port/portmkfile:3)- ../port/devusb.c
term% 

what's wrong?

On 2014/04/30, at 5:11, cinap_lenrek@felloff.net wrote:

> that might work. i havnt tried it. you need to be carefull
> with overflows as 2GB becomes negative with signed 32 bit ints.
> 
> 	if(dsize >= 0x80000000UL){	/* for sanity, overflow */
> 		werrstr("invalid allocation size");
> 		return nil;
> 	}
> 
> the only routine that does substantial allocation is iobufinit()
> in cwfs/malloc.c.
> 
> as far as i can see, this memory is never freed, so we might
> just remove the define:
> 
> all.h:13: #define malloc(n)	ialloc(n, 0)
> 
> and provide our own ialloc() that just uses brk().
> 
> --
> cinap



  reply	other threads:[~2014-04-30 14:41 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28  4:25 9FRONT "опен-сссл" Released sl
2014-04-28 10:52 ` cwfs fsmempercent arisawa
2014-04-28 17:08   ` [9front] " cinap_lenrek
2014-04-28 17:26   ` cinap_lenrek
2014-04-28 22:55     ` arisawa
2014-04-29 20:11       ` cinap_lenrek
2014-04-30 14:41         ` Kenji Arisawa [this message]
2014-04-30 20:14           ` cinap_lenrek
2014-05-01 10:39             ` 9pc64 arisawa
2014-05-01 11:07               ` [9front] 9pc64 Aram Hăvărneanu
2014-05-01 14:06                 ` arisawa
2014-05-01 14:25                   ` cinap_lenrek
2014-05-01 14:39                   ` cinap_lenrek
2014-05-01 15:27                   ` cinap_lenrek
2014-05-01 21:49                     ` Kenji Arisawa
2014-05-01 21:51                       ` cinap_lenrek
2014-05-01 23:22                         ` Kenji Arisawa
2014-05-01 23:34                         ` Kenji Arisawa
2014-05-02  0:22                           ` cinap_lenrek
2014-05-02 11:02                             ` Aram Hăvărneanu
2014-05-04  5:24                               ` malloc Kenji Arisawa
2014-05-04  8:22                                 ` [9front] malloc arisawa
2014-05-04 12:40         ` [9front] cwfs fsmempercent arisawa
2014-05-04 23:22           ` cinap_lenrek
2014-05-05  0:11             ` arisawa
2014-05-05  0:31               ` cinap_lenrek
2014-05-05  0:43                 ` cinap_lenrek
2014-05-05  2:04                   ` arisawa
2014-05-05  4:32                     ` cinap_lenrek
2014-05-05  8:00                       ` arisawa
2014-05-05 11:15                         ` arisawa
2014-05-05 12:08                           ` arisawa
2014-05-03  0:37   ` cinap_lenrek

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=CA794870-DE36-4C2B-85D9-F4C6C4F1385F@ar.aichi-u.ac.jp \
    --to=arisawa@ar.aichi-u.ac.jp \
    --cc=9front@9front.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).