From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.7pre6aa1
Date: Thu, 12 Jul 2001 10:16:35 +0200 [thread overview]
Message-ID: <20010712101635.C779@athlon.random> (raw)
Diff between 2.4.7pre5aa1 and 2.4.7pre6aa1:
Only in 2.4.7pre5aa1: 00_bh-async-2
Only in 2.4.7pre6aa1: 00_bh-async-3
Rediffed again due trivial rejects.
Only in 2.4.7pre5aa1: 00_drop___unlock_buffer-1
Only in 2.4.7pre5aa1: 00_drop_end_buffer_write-1
Only in 2.4.7pre5aa1: 00_kiobuf-backout-get_bh-1
Only in 2.4.7pre5aa1: 00_linus-brelse-fix-1
Merged in mainline.
Only in 2.4.7pre6aa1: 00_iput-debug-1
Minor debugging check.
Only in 2.4.7pre6aa1: 00_lvm-0.9.1_beta7-4_rwsem-fast-path-1
Converted the semaphores in the lvm very fast path to rwsemaphores, so
we never block on locks in the common case. I'd like to know
if this makes a difference to Oracle users. It is incremental
with lvm beta7 (that was just previously included into my tree).
Only in 2.4.7pre5aa1: 00_rwsem-14
Only in 2.4.7pre6aa1: 00_rwsem-15
Temporarily turned off alpha optimizations because they don't fit into
this framework, will turn them on ASAP.
Only in 2.4.7pre5aa1: 00_softirq-fixes-4
Only in 2.4.7pre6aa1: 00_softirq-fixes-5
Dropped the definition of smp_mb__ for the atomic_t operations that are
now in mainline (left the other parts).
Only in 2.4.7pre6aa1: 40_blkdev-pagecache-5
Now fixed also initrd, and tested that reads and writes with part of
the page beyond of the end of the device works (assuming userspace
knows where the device ends without relying on the last
readable/writeable byte, kernel doesn't destabilize if you write and
read beyond the end though).
Andrea
next reply other threads:[~2001-07-12 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 8:16 Andrea Arcangeli [this message]
2001-07-12 8:21 ` 2.4.7pre6aa1 Andrea Arcangeli
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=20010712101635.C779@athlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.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