Mark Hindley wrote:
I am running 2.4.0 final. I got the following failed paging request which
produced a complete freeze.
As you can see it was precipitated by cron starting to run some
housekeeping stuff overnight.
Has anyone else had prblems?
It looks real. It was executing this line
Jamie Lokier wrote:
Daniel Phillips wrote:
It was done last year, quietly and without fanfare, by Stephen Rothwell:
http://www.linuxcare.com/about-us/os-dev/rothwell.epl
This may be the most significant new feature in 2.4.0, as it allows us
to take a fundamentally different
Jamie Lokier wrote:
Daniel Phillips wrote:
[things that can benefit from dnotify]
locate (reindex only those directories that have changed, keep index
database current).
Not a chance. dnotify doesn't work recursively, so you can't monitor
just a few top level directories like "
Jamie Lokier wrote:
Daniel Phillips wrote:
DN_OPEN A file in the directory was opened
You open the top level directory and register for events. When somebody
opens a subdirectory of the top level directory, you receive
notification and register for events
Jesse Pollard wrote:
Daniel Phillips [EMAIL PROTECTED]:
Jamie Lokier wrote:
Daniel Phillips wrote:
DN_OPEN A file in the directory was opened
You open the top level directory and register for events. When somebody
opens a subdirectory of the top level
"David S. Miller" wrote:
2) It affects only code which can burn a lot of cpu without
scheduling. Compare this to schemes which make the kernel
fully pre-emptable, causing _EVERYONE_ to pay the price of
low-latency
Is there necessarily a
Keith Owens wrote:
I want to completely remove this multi layered method for setting
initialisation order and go back to basics. I want the programmer to
say "initialise E and F after G, H and I". The kernel build system
works out the directed graph of initialisation order then controls the
Joe deBlaquiere wrote:
Maybe I've been off in the hardware lab for too long, but how about
1. using ioperm to give access to the parallel port.
2. have your program write a byte (thread id % 256 ?) constantly to the
port during it's other activity
3. capture the results from another
Shawn Starr wrote:
This is not a kernel bug, This is a bug in the XFree86 TrueType rendering
extention. This has been discussed on the Xpert XFree86 mailing list. There
is a fix in the works (depends on the TrueType fonts your using).
A BUG is a BUG:
kernel BUG at slab.c:1542!
The kernel
Gregory Maxwell wrote:
On Wed, Jan 24, 2001 at 01:58:22PM +0100, Daniel Phillips wrote:
This is not a kernel bug, This is a bug in the XFree86 TrueType rendering
extention. This has been discussed on the Xpert XFree86 mailing list. There
is a fix in the works (depends on the TrueType
On Wed, 24 Jan 2001, David Wragg wrote:
"Benjamin C.R. LaHaise" [EMAIL PROTECTED] writes:
On 24 Jan 2001, David Wragg wrote:
[EMAIL PROTECTED] (Eric W. Biederman) writes:
Why do you need such a large buffer?
ext2 doesn't guarantee sustained write bandwidth (in particular,
"Stephen C. Tweedie" wrote:
We also maintain the
per-page buffer lists as caches of the virtual-to-physical mapping to
avoid redundant bmap()ping.
Could you clarify that one, please?
--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Michael Rothwell wrote:
Unfortunately, unix allows everything but "/" in filenames. This was
probably a mistake, as it makes it nearly impossible to augment the
namespace, but it is the reality.
For some reason totally beyond my comprehension // inside a file name is
taken to be the same as
Christoph Rohland wrote:
As of 2.4.1-pre we pin the pages by increasing the page count for
locked segments. No special list needed.
Sure no special list is needed. But without a special list to park
those pages on they will just circulate on the active/inactive lists,
wasting CPU cycles and
Rik van Riel wrote:
On Tue, 9 Jan 2001, Daniel Phillips wrote:
Linus Torvalds wrote:
(This is why I worked so hard at getting the PageDirty semantics right in
the last two months or so - and why I released 2.4.0 when I did. Getting
PageDirty right was the big step to make all
"Stephen C. Tweedie" wrote:
Hi,
On Thu, Jan 25, 2001 at 09:05:54PM +0100, Daniel Phillips wrote:
"Stephen C. Tweedie" wrote:
We also maintain the
per-page buffer lists as caches of the virtual-to-physical mapping to
avoid redundant bmap()ping.
Could
Rusty Russell wrote:
In message [EMAIL PROTECTED] you write:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0005.3/0269.html
A lot of the timer deletion races are hard to fix because of
the deadlock problem.
Hmmm...
For 2.5, changing the timer interface to disallow
On Tue, 30 Jan 2001, Rusty Russell wrote:
In message [EMAIL PROTECTED] you write:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0005.3/0269.html
A lot of the timer deletion races are hard to fix because of
the deadlock problem.
Hmmm...
For 2.5, changing the timer
On Tue, 30 Jan 2001, Manfred Spraul wrote:
This one is an UP and SMP race:
spin_unlock_irq(timerlist_lock);
+ if (timer-event)
+ {
+ if ((requeue = timer-event(data)))
+ {
+ timer-expires += requeue;
+ internal_add_timer(timer);
+ }
+ }
+ else
+ timer-function(data); /*
Timur Tabi wrote:
** Reply to message from David Woodhouse
Note that this is _precisely_ the reason I'm advocating the removal of
sleep_on(). When I was young and stupid (ok, "younger and stupider") I used
sleep_on() in my code. I pondered briefly the fact that I really couldn't
Here's an improved timer interface as suggested by Rusty and elaborated
by me. It turned out that the original problem I set out to solve was
already solved (and this approach would not have solved it anyway) but
there is a compelling reason for taking this seriously: there are four
fewer
On Wednesday 09 May 2001 23:22, you wrote:
Daniel writes [re index directories]:
This is lightly tested and apparently stable.
I was looking at the new patch, and I saw something that puzzles me.
Why do you set the EXT2_INDEX_FL on a new (empty) directory, rather
than only setting it when
On Thursday 10 May 2001 22:53, Andreas Dilger wrote:
OK, here are the patches described above.
The first one changes the use of the various INDEX flags, so that
they only appear when we have mounted with -o index (or
COMPAT_DIR_INDEX) and actually created an indexed directory.
The second
On Friday 11 May 2001 09:10, Andreas Dilger wrote:
and previously wrote:
OK, here are the patches described above.
Unfortunately, they haven't been tested. I've given them several
eyeballings and they appear OK, but when I try to run the ext2
index code (even without -o index mount
On Monday 07 May 2001 20:42, Pavel Machek wrote:
It's not exactly kernel-based fsck. What I've been talking
about is secondary filesystem providing coherent access to
primary fs metadata. I.e. mount -t ext2meta -o master=/usr none
/mnt and then access through /mnt/super,
On Friday 11 May 2001 18:34, Andreas Dilger wrote:
Al writes:
On Fri, 11 May 2001, Andreas Dilger wrote:
I've tested again, now with kdb, and the system loops in
ext2_find_entry() or ext2_add_link(), because there is a
directory with a zero rec_len. While the actual cause of this
On Monday 07 May 2001 08:26, Tobias Ringstrom wrote:
On Sun, 6 May 2001, David S. Miller wrote:
It is the most straightforward way to make a '1' or '0'
integer from the NULL state of a pointer.
But is it really specified in the C standards to be exctly zero or
one, and not zero and
On Sunday 13 May 2001 00:18, Alexander Viro wrote:
On Sat, 12 May 2001, Andreas Dilger wrote:
We could use the buffer_uptodate flag on the buffer to signal
that the block has been checked. AFAIK, a new buffer will not be
uptodate, and once it is it will not be read from disk again...
On Saturday 12 May 2001 23:41, Andreas Dilger wrote:
Daniel writes:
Oh yes, I'm well aware it, that's what I mean by the bullet
proofing item on my to-do list. I don't quite agree with the idea
of embedding the checking of directory entry format inside the
ext2_get_page routine, it
On Thursday 10 May 2001 09:21, Andreas Dilger wrote:
I previously wrote:
I was looking at the new patch, and I saw something that puzzles
me. Why do you set the EXT2_INDEX_FL on a new (empty) directory,
rather than only setting it when the dx_root index is created?
Setting the flag
On Monday 14 May 2001 07:15, Richard Gooch wrote:
Linus Torvalds writes:
But sure, you can use bmap if you want. It would be interesting to
hear whether it makes much of a difference..
I doubt bmap() would make any difference if there is a way of
controlling when the I/O starts.
On Monday 14 May 2001 06:00, Rik van Riel wrote:
+ if (!PageActive(page))
+ activate_page(page);
+ else
+ SetPageReferenced(page);
+
How about:
+ if (PageActive(page))
+ SetPageReferenced(page);
+ else
+
On Monday 14 May 2001 07:29, Blesson Paul wrote:
Hi
I am trying to implement a distributed file system.
For that I write a file driver. I want to know the following things
1 . If I am writing a new file system, is it necessary to modify the
existing structs including inode
On Monday 14 May 2001 20:33, Andreas Dilger wrote:
Danie, you write:
This can go in ext2_bread, which already has dir-specific code in
it (readahead), and ext2_getblk remains generic, for what it's
worth.
Note that the dir-specific code in ext2_bread() is not readahead, but
rather
On Monday 14 May 2001 20:33, Andreas Dilger wrote:
Daniel, you write:
Now, if the check routine tells us how much good data it found we
could use that to set a limit for the dirent scan, thus keeping the
same robustness as the old code but without having all the checks
in the inner loop.
On Monday 14 May 2001 22:04, Andreas Dilger wrote:
Maybe we can have a noindex mount option for this?
We need that regardless, I just keep forgetting to put it in. I assume
the semantics are obvious: no new indexes are created but existing ones
are maintained. I.e., -o noindex does not mean
On Monday 14 May 2001 22:04, Andreas Dilger wrote:
Daniel writes:
I was originally thinking we should give the admin the ability to
create a nonindexed directory if desired, and that's how it used to
be before we changed the setting of INDEX_FL from directory
creation time to later, when
On Tuesday 15 May 2001 01:19, Richard Gooch wrote:
Linus Torvalds writes:
On Sun, 13 May 2001, Richard Gooch wrote:
So, why can't the page cache check if a block is in the buffer
cache?
Because it would make the damn thing slower.
The whole point of the page cache is to be FAST
On Tuesday 15 May 2001 08:57, Alexander Viro wrote:
On Tue, 15 May 2001, Richard Gooch wrote:
What happens if you create a buffer cache entry? Does that
invalidate the page cache one? Or do you just allow invalidates
one way, and not the other? And why=
I just figured on one way
On Tuesday 15 May 2001 12:44, Alexander Viro wrote:
On Tue, 15 May 2001, Daniel Phillips wrote:
That's because you left out his invalidate:
* create an instance in pagecache
* start reading into buffer cache (doesn't invalidate, right?)
* start writing using pagecache
On Tuesday 15 May 2001 23:20, Nicolas Pitre wrote:
Personally, I'd really like to see /dev/ttyS0 be the first detected
serial port on a system, /dev/ttyS1 the second, etc.
There are well-defined rules for the first four on PC's. The ttySx
better match the labels the OEM put on the box.
--
On Tuesday 15 May 2001 22:51, Linus Torvalds wrote:
On Tue, 15 May 2001, Alexander Viro wrote:
If you want them all to inherit it - inherit from mountpoint.
..which is exactly what the device node ends up being. The implicit
mount-point.
And which point, btw, it is completely
On Tuesday 15 May 2001 17:34, Linus Torvalds wrote:
On Tue, 15 May 2001, Neil Brown wrote:
Ofcourse setting the queue function that __blk_get_queue call to
do a lookup of the minor and choose an appropriate queue for the
real device wont work as you need to munge bh-b_rdev too.
What I
Sorry, I couldn't think of any good flames that haven't already been
posted so I thought I'd be boring and post some code. ;-)
On Monday 14 May 2001 23:50, Daniel Phillips wrote:
On Monday 14 May 2001 20:33, Andreas Dilger wrote:
Daniel, you write:
Now, if the check routine tells us how
On Friday 18 May 2001 00:06, Dan Kegel wrote:
Tomas Telensky ([EMAIL PROTECTED]) wrote:
does anybody know about any archive/digest service for this mailing
list? Majordomo at vger doesn't support this. Or does anybody of
you archive all e-mails?
[...]
See
On Friday 18 May 2001 17:11, Arjan van de Ven wrote:
(a) Back off the capability approach. That is, accept that
people doing configuration are going to explicitly and
exhaustively specify low-level hardware.
snip
I don't want to do (a); it conflicts with my design
(I think?) and the
other 4 on a tower conected to the RAID, which will be have the
cache of the squid server.
[...]
also appropriate could be ext2 with daniel phillips' directory
indexing patches.
The ext2 indexing patch is apparently stable but it's still pre-alpha
until the hash function
On Saturday 19 May 2001 18:33, Rik van Riel wrote:
On Sat, 19 May 2001, [iso-8859-1] Jakob Østergaard wrote:
What do you think of this ?
[root]# cat /proc/sys/fs/inode-nr
157097 -180
I think you should upgrade to a newer kernel; Al Viro
fixed this bug and the fix went into
On Tuesday 22 May 2001 02:59, Keith Owens wrote:
# Not a real dependency, this checks for hand editing of .config.
$(KBUILD_OBJTREE)include/linux/autoconf.h: $(KBUILD_OBJTREE).config
@echo Your .config is newer than include/linux/autoconf.h,
this should not happen. @echo Always run
On Tuesday 22 May 2001 04:41, Ricardo Galli wrote:
Hi,
you can find at http://bulma.lug.net/static/ a few new benchmarks
among Reiser, XFS and Ext2 (also one with JFS).
This time there is a comprehensive Hans' Mongo benchmarks
(http://bulma.lug.net/static/mongo/ )and a couple of
On Tuesday 22 May 2001 12:29, Daniel Phillips wrote:
The measured create and rename times for Ext2 look pretty silly,
don't they? OK, I know that my htree directory index patch isn't part
of Ext2 yet, but at least lets mention that this is a solved problem.
http://nl.linux.org/~phillips
On Tuesday 22 May 2001 16:42, john slee wrote:
On Mon, May 21, 2001 at 10:00:07PM +0200, Urban Widmark wrote:
On Mon, 21 May 2001, Eric S. Raymond wrote:
the NEW tag). That phase ended almost a month ago. Nobody who
has actually tried the CML2 tools more recently has reported that
On Tuesday 22 May 2001 20:20, David N. Lombard wrote:
Rik van Riel wrote:
On Tue, 22 May 2001, Daniel Phillips wrote:
On Tuesday 22 May 2001 12:29, Daniel Phillips wrote:
http://nl.linux.org/~phillips/htree
Oops, nl.linux.org was down for 'unscheduled maintainance' and
seems
On Wednesday 23 May 2001 06:19, Edgar Toernig wrote:
Daniel Phillips wrote:
On Tuesday 22 May 2001 17:24, Oliver Xymoron wrote:
On Mon, 21 May 2001, Daniel Phillips wrote:
On Monday 21 May 2001 19:16, Oliver Xymoron wrote:
What I'd like to see:
- An interface
On Wednesday 23 May 2001 09:33, Marcelo Tosatti wrote:
Hi,
I just noticed a bad effect of write drop behind yesterday during
some tests.
The problem is that we deactivate written pages, thus making the
inactive list become pretty big (full of unfreeable pages) under
write intensive IO
On Tuesday 22 May 2001 17:24, Oliver Xymoron wrote:
On Mon, 21 May 2001, Daniel Phillips wrote:
On Monday 21 May 2001 19:16, Oliver Xymoron wrote:
What I'd like to see:
- An interface for registering an array of related devices
(almost always two: raw and ctl) and their legacy
On Tuesday 22 May 2001 19:49, Oliver Xymoron wrote:
On Tue, 22 May 2001, Daniel Phillips wrote:
I don't think it's likely to be even workable. Just consider the
directory entry for a moment - is it going to be marked d or
[cb]?
It's going to be marked 'd', it's a directory
On Friday 25 May 2001 00:00, Hans Reiser wrote:
Daniel Phillips wrote:
I suppose I'm just reiterating the obvious, but we should
eventually have a generic filesystem transaction API at the VFS
level, once we have enough data points to know what the One True
API should be.
Daniel
On Thursday 24 May 2001 22:59, Edgar Toernig wrote:
Daniel Phillips wrote:
Readdir fills in a directory type, so ls sees it as a directory
and does the right thing. On the other hand, we know we're on
a device filesystem so we will next open the name as a regular
file, and find
On Wednesday 23 May 2001 06:19, Edgar Toernig wrote:
IMO the whole idea of arguments following the device name is junk
(incl a /ctrl).
You know I didn't suggest that, right? I find it pretty strange too, but
I'm listening to hear the technical arguments.
Just think about the implications of
On Saturday 26 May 2001 05:07, Edgar Toernig wrote:
Daniel Phillips wrote:
Oops, oh wait, there's already another open point: your breakage
examples both rely on opening .. You're right, . should always
be a directory and I believe that's enforced by the VFS. So we
don't have
On Saturday 19 May 2001 08:23, Ben LaHaise wrote:
/dev/sda/offset=1024,limit=2048
- open a device that gives a view of sda at an
offset of 1KB to 2KB
Whatever we end up with, can we express it in terms of base, size,
please?
--
Daniel
-
To unsubscribe
On Monday 21 May 2001 14:43, [EMAIL PROTECTED] wrote:
How about:
# mkpart /dev/sda /dev/mypartition -o size=1024k,type=swap
# ls /dev/mypartition
basesizedevicetype
Generally, we shouldn't care which order the kernel enumerates
devices in or which
On Monday 21 May 2001 10:14, Lars Marowsky-Bree wrote:
On 2001-05-19T16:25:47,
Daniel Phillips [EMAIL PROTECTED] said:
How about:
# mkpart /dev/sda /dev/mypartition -o size=1024k,type=swap
# ls /dev/mypartition
base sizedevice type
# cat /dev/mypartition/size
On Thursday 24 May 2001 02:23, Edgar Toernig wrote:
Daniel Phillips wrote:
It's going to be marked 'd', it's a directory, not a file.
Aha. So you lose the S_ISCHR/BLK attribute.
Readdir fills in a directory type, so ls sees it as a directory and
does the right thing
On Wednesday 30 May 2001 17:25, Ingo Molnar wrote:
On Wed, 30 May 2001, Nico Schottelius wrote:
the default value is 0, that is good enough.
hmm.. I don't think so... value of 1 would be much better, because
0 normally disables the speaker.
i confused the value. Yes, an initialization
Changes:
- Freshen to 2.4.5
- EXT2_FEATURE_COMPAT_DIR_INDEX flag finalized
- Break up ext2_add_entry for aesthetic reasons (Al Viro)
- Handle more than 64K directories per directory (Andreas Dilger)
- Bug fix: new inode no longer inherits index flag (Andreas Dilger)
- Bug fix:
On Thursday 31 May 2001 21:44, Andreas Dilger wrote:
Daniel, you write:
- Fall back to linear search in case of corrupted index
OK, I have _some_ of the code needed to do this, but in one case I'm
not sure of what your intention was - in dx_probe() you check for
unused_flags 1 to signal
On Tuesday 22 May 2001 22:10, Andreas Dilger wrote:
Peter Braam writes:
File system journal recovery can corrupt a snapshot, because it
copies data that needs to be preserved in a snapshot. During
journal replay such data may be copied again, but the source can
have new data already.
On Thursday 31 May 2001 21:44, Andreas Dilger wrote:
I noticed something interesting when running mongo with debugging
on. It is adding filenames which are only sequential numbers, and the
hash code is basically adding to only two blocks until those blocks
are full, at which point (I guess)
Nathan Paul Simons wrote:
As for the argument of putting it in the kernel being more robust and
idiot-proof, well, if someone can't keep three files and one directory
straight for each different configuration of the kernel that they want to
play with, they probably shouldn't be
Linda Walsh wrote:
It may not matter too too much, but blocks are being passed around as
'ints'. On the ia32 architecture, this implies a maximum of 512*2G-1T
disk size. Probably don't need to worry about this today, but in a few
years? Should we be changing the internal interfaces to use
Arjan van de Ven wrote:
In article [EMAIL PROTECTED] you
wrote:
Well, the bug seems to exactly using the page after a "free_page()". Which
is always a bug, but at least should be easy to fix.
I've considered making "free_page()" a macro something like
__free_page(x);
Mike Jagdis wrote:
I disagree. No one here is dumb enough to use a wholely inappropriate
tool for a particular task. But using a debugger is often (but not
always) like sawing bits off your 2x4 until it happens to fit the
gap. What you need to do is to understand the problem parameters,
Mike Galbraith wrote:
On Wed, 6 Sep 2000, Damien Miller wrote:
Tools like a KDB would make the kernel a lot more accessible to the
time-poor.
Kdb is available to all. I think it should be _integrated_ mostly
because of the (potential) improvement in bug report quality.
Well, yes
Linus Torvalds wrote:
And quite frankly, for most of the real problems (as opposed to the stupid
bugs - of which there are many, as the latest crap with "truncate()" has
shown us) a debugger doesn't much help. And the real problems are what I
worry about. The rest is just details. It will
Christer Weinigel wrote:
[[EMAIL PROTECTED]] wrote:
I'm really kind of surprised that companies like SuSE, VA and RedHat
haven't started talking about forking the kernel already. Those companies
are serving the administrators and managers whose needs you are openly
admitting that you are
Alexander Viro wrote:
On Fri, 1 Sep 2000, Tigran Aivazian wrote:
Rasmus, you introduced a bug because you removed the code but left the
comment around. now /* this should go into -truncate */ is there and very
confusing - what should go into -truncate?
... except that comment is
Linus Torvalds wrote:
It's not whether you can use tools to do the work.
It's about what kind of people you get.
This makes a lot of sense. Stop there and you are done. But...
...in the end, maybe the rule to only use hand power makes sense. Not
because hand-power is _better_. But
Jamie Lokier wrote:
Michael Elizabeth Chastain wrote:
A source control system so that curious people could do the equivalent of
"cvs annotate" and figure out who wrote particular pieces?
Note convinced about "cvs annotate". Maybe annotation with version
numbers. But "cvs diff"
podda wrote:
i'm a linux newbie trying to learn kernel magic. i would be glad if
someone can advice me where to look for to get an idea of the linux
kernel. hey i don't need that one. ( "use the force, read the source" )
i already tried to use the force , but can't figure out where i
Marco Colombo wrote:
BTW, a kernel debugger *is* available. And maybe even a more powerful
one will be if Jeff decides to port and publicly release it.
One that subject, I would *love* to take the time to see how small a
subset of Ext2 I could write to have a (mostly) non-invasive source
code
Andi Kleen wrote:
On Thu, Sep 14, 2000 at 02:21:44PM +0200, Daniel Phillips wrote:
The hardest problem: how do you do the block read? Possibilities:
- Ignore the problem, use normal block device I/O
- Use the real mode bios, needs V86 support
And it requires a sync before every
Keith Owens wrote:
* Standardize on tracking the System.map and .config with the kernel.
There was a suggestion from Alan Cox that .config.gz be appended to
bzImage, after the part that gets loaded into memory, to which I added
the suggestion that System.map.gz also be appended. That about
Here we are, finally: code. I do not make any claim that this code is
elegant, correct, complete, esthetically pleasing or that it will
refrain from eating your hard disk.
What this code will do is let you verify for yourself whether my
proposed approach to tailmerging for Ext2 is worth the
Alexander Viro wrote:
On Sun, 17 Sep 2000, Linus Torvalds wrote:
On Sun, 17 Sep 2000, Alexander Viro wrote:
Looks sane. But I really wonder if we could just do it in
create_page_buffers() if page is up-to-date. OTOH it would require attempt
to map them all. Comments?
Alexander Viro wrote:
On Mon, 18 Sep 2000, Andreas Dilger wrote:
Alexander writes:
* uptodate pages should never become non-uptodate.
uptodate .. pages ... never have data _older_ than on disk
This may actually be a problem in the future... what about shared access
Linus Torvalds wrote:
On Mon, 18 Sep 2000, Alexander Viro wrote:
That's what makes me unhappy about the current situation + obvious
fixes. It works, but the proof is... well, not pretty.
Oh, agreed. I think we should clean up the code. I looked at it yesterday,
and it didn't look
Andreas Dilger wrote:
Daniel writes:
Alexander Viro wrote:
On Mon, 18 Sep 2000, Andreas Dilger wrote:
This may actually be a problem in the future... what about shared access
block devices like FCAL or a distributed filesystem? It has to be
possible for pages to become
Linus Torvalds wrote:
On Mon, 18 Sep 2000, Alexander Viro wrote:
* we have several bh state components and the thing is a big,
fscking mess. If we look at the areas outside of the page lock we have:
It's not a mess at all.
I don't see why you call things "first stage" etc. It's
Alexander Viro wrote:
On Tue, 19 Sep 2000, Daniel Phillips wrote:
The more I think about it the less clear and ambiguous I find it.
When you add the dirty bit into the pot you get:
Mapped, Uptodate, Dirty: not possible
Sure, it is possible - that's how the write happens
Daniel Phillips wrote:
Alexander Viro wrote:
On Tue, 19 Sep 2000, Daniel Phillips wrote:
!Mapped, !Uptodate, Dirty: pending map and write
Wrong. It's an instant BUG at line 711 in ll_rw_blk.c - remember these
reports?
Yes, correct, this state should not escape from
Keith Owens wrote:
On Wed, 20 Sep 2000 17:09:27 +0800 (CST),
[EMAIL PROTECTED] wrote:
I would like to upgrade my kernel which is bundled with Red Hat.
Ask redhat for the .config, this is not a problem for the linux-kernel list.
I'd just like to remind you of Alan Cox's suggestion about
Marc Lehmann wrote:
On Sat, Sep 16, 2000 at 10:59:54PM +0200, Daniel Phillips
[EMAIL PROTECTED] wrote:
Here we are, finally: code. I do not make any claim that this code is
elegant, correct, complete, esthetically pleasing or that it will
refrain from eating your hard disk.
What
Keith Owens wrote:
Daniel Phillips [EMAIL PROTECTED] wrote:
I'd just like to remind you of Alan Cox's suggestion about appending
.config.gz to bzImage so that it doesn't get loaded into memory, and
my suggestion to put System.map.gz there as well.
I worry about anything that increases
Andreas Haumer wrote:
Keith Owens wrote:
I worry about anything that increases the on disk size of bzImage, even
if the extra data does not get loaded into kernel memory.
You also have to consider filesize restrictions with some
network bootproms loading the kernel image with TFTP.
Daniel Phillips wrote:
I see that Ingo Molnar has been working on a btree directory extension for Ext2...
Oops, I mispoke, Ted Ts'o is actually doing that work, sorry Ted. Um,
did it work?
--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
Keith Owens wrote:
Brian Gerst [EMAIL PROTECTED] wrote:
Currently, System.map contains a significant number of automatically
generated symbols. These symbols are unnecessary for debugging since
they represent individual elements of the exported symbol and PCI device
tables, yet represent
Anton Altaparmakov wrote:
I can't remember anything about protected mode interrupt handlers nor have
I ever looked at Linux interrupt handling but at least in real mode from my
good old PC/DOS programming days I seem to remember that if you are hooking
a hardware interrupt vector then you
Benjamin Herrenschmidt wrote:
Hmm, good idea, but how does this work on, say, non-x86 architectures
which don't have a VGA text frame buffer, or whose VGA text frame buffer
is not mapped in, or whose VGA text frame buffer is not initialised.
You will still end up with those "my kernel
1 - 100 of 1437 matches
Mail list logo
