On Sun Apr 15 2001 - 15:57:52, EST Amit D Chaudhary ([EMAIL PROTECTED]) wrote:
> On the same topic, I have not found any change in free memory reported before
> and after the ioctl call. Though umount /initrd does free around 2 MB.
I have found the same thing - that umount /initrd seems to
On Sun Apr 15 2001 - 15:57:52, EST Amit D Chaudhary ([EMAIL PROTECTED]) wrote:
On the same topic, I have not found any change in free memory reported before
and after the ioctl call. Though umount /initrd does free around 2 MB.
I have found the same thing - that umount /initrd seems to
On 15 Apr 2001, H. Peter Anvin wrote:
> Followup to: <[EMAIL PROTECTED]>
> By author:Amit D Chaudhary <[EMAIL PROTECTED]>
> In newsgroup: linux.dev.kernel
> >
> > On the same topic, I have not found any change in free memory
> > reported before and after the ioctl call. Though umount
Followup to: <[EMAIL PROTECTED]>
By author:Amit D Chaudhary <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> On the same topic, I have not found any change in free memory
> reported before and after the ioctl call. Though umount /initrd does
> free around 2 MB.
>
With Scott's patch
Followup to: <[EMAIL PROTECTED]>
By author:Scott Murray <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Indeed it is. This fix for drivers/block/rd.c (excerpted from 2.4.3-ac6):
>
This did the trick. I bounced the patch to Linus, too.
-hpa
--
<[EMAIL PROTECTED]> at
On the same topic, I have not found any change in free memory reported before
and after the ioctl call. Though umount /initrd does free around 2 MB.
Amit
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
On 14 Apr 2001, H. Peter Anvin wrote:
> Hello friends,
>
> I am trying the following setup, and it works beautifully, *except*
> that I don't seem to be able to free the ramdisk memory at the end.
Heh, sounds familiar, I was in exactly the same situation a month ago.
I meant to post something
Hello friends,
I am trying the following setup, and it works beautifully, *except*
that I don't seem to be able to free the ramdisk memory at the end.
This is using the 2.4.3 stock kernel:
I load an initrd in "non-initrd" mode:
label single
kernel vmlinuz
append
Hello friends,
I am trying the following setup, and it works beautifully, *except*
that I don't seem to be able to free the ramdisk memory at the end.
This is using the 2.4.3 stock kernel:
I load an initrd in "non-initrd" mode:
label single
kernel vmlinuz
append
On 14 Apr 2001, H. Peter Anvin wrote:
Hello friends,
I am trying the following setup, and it works beautifully, *except*
that I don't seem to be able to free the ramdisk memory at the end.
Heh, sounds familiar, I was in exactly the same situation a month ago.
I meant to post something about
On the same topic, I have not found any change in free memory reported before
and after the ioctl call. Though umount /initrd does free around 2 MB.
Amit
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
Followup to: [EMAIL PROTECTED]
By author:Scott Murray [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
Indeed it is. This fix for drivers/block/rd.c (excerpted from 2.4.3-ac6):
This did the trick. I bounced the patch to Linus, too.
-hpa
--
[EMAIL PROTECTED] at work, [EMAIL
Followup to: [EMAIL PROTECTED]
By author:Amit D Chaudhary [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
On the same topic, I have not found any change in free memory
reported before and after the ioctl call. Though umount /initrd does
free around 2 MB.
With Scott's patch applied,
On 15 Apr 2001, H. Peter Anvin wrote:
Followup to: [EMAIL PROTECTED]
By author:Amit D Chaudhary [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
On the same topic, I have not found any change in free memory
reported before and after the ioctl call. Though umount /initrd does
free
14 matches
Mail list logo
