¾È³ç Çϼ¼¿ä... ´Ù¸§ÀÌ ¾Æ´Ï¶ó Á¦°¡ À̹ø¿¡ °¡Áö°í
ÀÖ´Â ¸ðµç µ·À» °¡Áö°í ¼îÇθôÀ» ¿ÀÇ ÇÏ¿´½À´Ï´Ù. ¾î·Á¿î »óȲ¿¡ ¿ÀÇÂÇÑ ÅͶó ³Ê¹«³ª Èûµç »óȲ ÀÔ´Ï´Ù. ÀúÈñ »çÀÌÆ®¿¡ ¿À¼Å¼
µû¶æÇÑ ÇѸ¶µð ºÎŹ µå¸³´Ï´Ù. www.najababara.co.kr , www.najababara.com °°Àº °÷ ÀÔ´Ï´Ù. ±×¸®°í
¹«¸®ÇÑ ºÎŹÀÌÁö¸¸ ¸¹Àº ºÐ
Title: ¾ÆÀ̵ûµûµû
³×ƼÁðÀÌ ÁÖÀÎÀÌµÇ¾î ¸¸µå´Â °Ë»ö¿£Áø ¾ÆÀ̵ûµûµû ¼Ò°³
more
»
> I think we should certainly use vm_copy for whole-page copies in
> pager_memcpy because of the badly suboptimal behavior you've described.
I have cooked up the attached implementation. I checked everything
but a few border cases -- I need to write a few more tests. Perhaps,
I will get to it t
Title: Àý´ë ¼ºÀθ¸ Ŭ¸¯ÇÏ½Ã°í ¹Ì¼º³âÀÚ´Â Áö¿ì¼¼¿ä.
Àý´ë ¼ºÀθ¸ Ŭ¸¯ÇÏ½Ã°í ¹Ì¼º³âÀÚ´Â Áö¿ì¼¼¿ä.
»õ·Î¿î
½ÅÁ¾ ¼ºÀε¿¿µ»ó À帣
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
1:1 ÀÎÅÍ³Ý ¿î¼¼»ó´ã
Çã¶ô¾øÀÌ ¸ÞÀÏ µå·Á¼
Á¤¸»ÁË¼Û ÇÕ´Ï´Ù. ¼öÀÔ±ÝÀº ¾î·Á¿î ÀÌ¿ôµ½±â¿¡ »ç¿ëÇÏ¿À´Ï
ÀÌÇØÇÏ¿© ÁÖ½Ç±æ ºÎŹµå¸®¸ç ¿øÄ¡ ¾ÊÀ¸½Ã¸é ¼ö½Å°ÅºÎ ÇÏ¿©ÁÖ½Ê½Ã¿ä ´Ù½Ã´Â º¸³»Áö ¾Ê°Ú½À´Ï´Ù,Á¤¸»ÁË
Title: Àý´ë ¼ºÀθ¸ Ŭ¸¯ÇÏ½Ã°í ¹Ì¼º³âÀÚ´Â Áö¿ì¼¼¿ä.
Àý´ë ¼ºÀθ¸ Ŭ¸¯ÇÏ½Ã°í ¹Ì¼º³âÀÚ´Â Áö¿ì¼¼¿ä.
»õ·Î¿î
½ÅÁ¾ ¼ºÀε¿¿µ»ó À帣
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
Title: ¸ÅÁ÷ÀÌÁö
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
Title: Aristotle
Your email address was obtained from an opt-in list, Reference #R64391. If you wish to unsubscribe from this list, please Click Here and send from this e-mail address. If you have previously unsubscribed
> This is on my good old Sparc station 4, a reasonably modern (low-end,
> less than two years old) IBM scsi disk, and linux-2.2.19. I'd expect
> more idle cycles on a modern machine and decent disk hardware, but I
> don't have any around.
You need to consider the correlation between the cpu speed
[EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
> So on the Hurd, you had 30%, and on Linux, you have 60%?
Sorry, it seems I was too careless when reading Ludovic Courtès'
message, I read "most of the cpu time" but missed the parenthesis
saying "30 %".
But anyway, for a performance compariso
[EMAIL PROTECTED] (Niels Möller) writes:
> The numbers depend a lot on the actual hardware, and the relative
> speed of the cpu and disks, I think. I just tried extracting
> gcc-3.0.4.tar (note, no .gz, unzipping would soak up most of the idle
> time). top reported that the tar process consumed a
[EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
> [EMAIL PROTECTED] (Niels Möller) writes:
>
> > Perhaps idling, waiting for disk i/o requests to complete?
>
> Do a big tar extraction on Linux and note that your tar process soaks
> up plenty of CPU time.
The numbers depend a lot on the actua
Thanks. I have applied everything but the libnetfs changes.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
--- Neal H Walfield <[EMAIL PROTECTED]> wrote:
> > Here is the follow-up patch that allows netfs_make_protid to only set
> errno
> > on failure.
>
> I am not really interested in this patch: I think
> netfs_make_{protid,peropen} should, in this regard, be changed to use
> similar semantics as
[EMAIL PROTECTED] (Niels Möller) writes:
> Perhaps idling, waiting for disk i/o requests to complete?
Do a big tar extraction on Linux and note that your tar process soaks
up plenty of CPU time.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail
[EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
> Ludovic Courtès <[EMAIL PROTECTED]> writes:
>
> > This kind of observation is quite normal I guess, due to the extensive use of
> > RPCs and so on, but are there still some optimizations that could be
> > implemented in order to reduce CPU consu
[EMAIL PROTECTED] (Niels Möller) writes:
> [EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
>
> > I have a more concrete idea about how to change diskfs into an
> > "ordered writes" instead of a "synchronous writes" model. If someone
> > prods me, I can explain it.
>
> Please do.
Suppose disk
--- Ludovic Courtès <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I tried to use the mtools on /dev/fd0 (which was translated by /hurd/storeio
> fd0) and it seems that the underlying Mach driver has a defect. When typing
> `mdir', I first got a segfault, then "No files." and then the whole system
> got f
Á¤º¸Åë½ÅºÎ ±Ç°í »çÇ׿¡ ÀǰŠÁ¦¸ñ¿¡
[±¤°í]¶ó°í Ç¥±âÇÑ ±¤°í ¸ÞÀÏÀÔ´Ï´Ù.¼ö½ÅÀ» ¿øÄ¡ ¾ÊÀ¸½Ã¸é
¼ö½Å°ÅºÎ¸¦
´·¯ÁÖ¼¼¿ä
°ÆÁ¤¸¶¼¼¿ä
ÀÏ´Ü ÇÑ ¹ø ¹«·á °ßÀûÀ» ¹Þ¾Æ º¸¼¼¿ä.
ÀÌ»ç ºñ¿ëÀÇ 10%¸¦ ÇöÂû·Î µ¹·Á µå¸³´Ï´Ù.
±×¸®°í ÀúÈñ¿Í °è¾àÀ» ÇϽŠºÐ Áß ÇѺÐÀ» Ãß÷ÇÏ¿©
¹«·á·Î ÀÌ»ç ÇØ µå¸³´Ï´Ù.
¾ó¸¶³ª ¾ç½ÉÀûÀÎ »
Ludovic Courtès <[EMAIL PROTECTED]> writes:
> This kind of observation is quite normal I guess, due to the extensive use of
> RPCs and so on, but are there still some optimizations that could be
> implemented in order to reduce CPU consumption?
Where do you think the processor should be spending
On Tue, Mar 26, 2002 at 09:58:17AM +0100, Oystein Viggen wrote:
> * [Jeroen Dekkers]
>
> > On Mon, Mar 25, 2002 at 09:59:14PM +0100, Farid Hajji wrote:
> >> All in all, binary compatibility is a nice thing to have.
> >
> > If it's only used for running non-free software I disagree.
>
> I can se
°³²
IT ±³À°¼¾ÅÍ ±³À°»ý ¸ðÁý¾È³»
James Morrison wrote:
>>+#define NBUCKETS (31 - LOG2_MIN_SIZE + 1)
>
> Why are you using 31 + 1 instead of just 32?
NBUCKETS must contain the number of elements between LOG2_MIN_SIZE
and 31 inclusively. This calculation is more logical.
--
Ognyan Kulev <[EMAIL PROTECTED]>, "\"Programmer\
Title: mail_main---
-. º» ¸ÞÀÏÀº Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü Á¦ 50Á¶¿¡ ÀǰÅÇÑ [±¤°í] ¸ÞÀÏÀÔ´Ï´Ù.
-. e-mail ÁÖ¼Ò´Â ÀÎÅͳݻ󿡼 ÃëµæÇÏ¿´À¸¸ç, ÁÖ¼ÒÀÌ¿Ü ¾î¶°ÇÑ °³ÀÎ Á¤º¸µµ °¡Áö°í ÀÖÁö ¾Ê½À´Ï´Ù.
* [Jeroen Dekkers]
> On Mon, Mar 25, 2002 at 09:59:14PM +0100, Farid Hajji wrote:
>> All in all, binary compatibility is a nice thing to have.
>
> If it's only used for running non-free software I disagree.
I can see no other reason. As you said, if it's free, we just recompile
it. Then we ca
Title: ³×¿À¿¡¹ö - ¾î¸¥µéÀÇ ÀÎÅÍ³Ý ¼¼»ó
¡Ø º» ¸ÞÀÏÀº Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü Á¦ 50Á¶¿¡ ÀǰÅÇÑ [±¤°í] ¸ÞÀÏÀÔ´Ï´Ù
¡Ø e-mailÁÖ¼Ò´Â ÀÎÅͳݻ󿡼 ÃëµæÇÏ¿´À¸¸ç, ÁÖ¼Ò¿Ü ¾î¶°ÇÑ °³ÀÎ Á¤º¸µµ °¡Áö°í ÀÖÁö ¾Ê½À´Ï´Ù
¡Ø DB¿À·ù·Î ÀÎÇÏ¿© ¾à°£ÀÇ ¸ÞÀÏÀÌ º¹¼ö¹ß¼Û µÉ¼ö ÀÖ½À´Ï´Ù. ¾Æ·¡ ´ã´ç
26 matches
Mail list logo