On Wed, Feb 02, 2005 at 10:44:14PM -0500, Ethan Weinstein wrote:
Hey all,
I've been having quite a time with the e1000 driver running at gigabit
speeds. Running it at 100Fdx has never been a problem, which I've done
done for a long time. Last week I picked up a gigabit switch, and that's
On Wed, Feb 02 2005, Andrew Morton wrote:
Dave Olien [EMAIL PROTECTED] wrote:
+extern inline void zero_fill_bio(struct bio *bio)
+{
+ unsigned long flags;
+ struct bio_vec *bv;
+ int i;
+
+ bio_for_each_segment(bv, bio, i) {
+ char *data = bvec_kmap_irq(bv,
Hi Vivek and Eric,
IMHO, why don't we swap not only the contents of the top 640K
but also kernel working memory for kdump kernel?
I guess this approach has some good points.
1.Preallocating reserved area is not mandatory at boot time.
And the reserved area can be distributed in small pieces
On Wednesday 02 February 2005 17:27, Peter Osterlund wrote:
On Wed, 2 Feb 2005, Dmitry Torokhov wrote:
On Wed, 02 Feb 2005 13:52:03 -0800 (PST), Peter Osterlund
[EMAIL PROTECTED] wrote:
if (mousedev-touch) {
+ size = dev-absmax[ABS_X] - dev-absmin[ABS_X];
+
Hi,
On 02 Feb 2005 08:24:03 -0700
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
So the kernel+initrd that captures a crash dump will live and execute
in a reserved area of memory. It needs to know which memory regions
are valid, and it needs to know small things like the final register
601 - 605 of 605 matches
Mail list logo
