[lkml]   [2001]   [Sep]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Linux 2.4.10-pre11
On Tue, Sep 18, 2001 at 02:19:42PM -0400, Alexander Viro wrote:
> with Andrea and once he gets back to life (no, 'e's just sleepin') we'll

yes, I'm back to life but I had a surprise: but my ISP is down so I'm
now masqueraded my dekstop over a wirless GPRS link via irda on the
laptop [GRPS is flat rate in Italy :) ] so it's quite dogslow at the
moment, I cannot read emails and RTT over GSM is of the order of 1
second (but I can send emails and slowly browse the web). I still hope
the ISP returns alive before tomorrow... (I'm looking into Andrew's
report at the moment and I don't need good connectivity for debugging it
luckily :)

I think the bug we have in the inode pinning isn't a showstopper (I
probably could live with it forever without ever have chance to notice it),
so no user should be hurted by it [but I understand it can hurt you very
much], and I am _very_ concerned in addressing it ASAP and I'm very
happy you spoteed it immediatly. I'll also check your worries with the
ramdisk BLKFLSBUF (the logic should be just like before the changes, the
reason I backed out the rd_bdev changes is because I was always working
with inodes for everything related to the physical address space, not
with bdevs so I didn't see a value in the change, but after the bugfix
[bdev->bd_mapping] probably this will change), for the other issue with the
->writepage as said it is fine and intentional, except we can do
something more efficient for the ramdisk adding some special case to the
memory balancing code (for istance we could always put the ramdisk stuff
over the active list rather than rolling it over in the inactive list
again, but quite frankly that's low prio unless somebody has a real
patological case and of course that applies and it always applied to
ramfs too [I did it with the argument: it works for ramfs so it will
obviously work work for ramdisk too]). In the next days I'll also be
very busy with some non linux-kernel developement issue, but I'll try to
be still as much responsive as possible for anything urgent (I'll
certainly be 100% responsive again next week starting from Wed 26).

At the moment my very first prio is to address the BUG() reported by
Andrew (if it is just been fixed please somebody at SuSE send me an SMS
so I don't waste time since as said I cannot read emails at the moment).

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:03    [W:0.112 / U:0.136 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site