All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@kvack.org>
To: axboe@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: reducing max segments expected to work?
Date: Wed, 11 May 2005 17:47:49 -0400	[thread overview]
Message-ID: <20050511214749.GA14072@kvack.org> (raw)

Hello Jens et al,

Is reducing the max number of segments in the block layer supposed to 
work (as done in the patch below), or should i be sticking to mucking 
with MAX_PHYS_SEGMENTS?  I seem to get a kernel thatt cannot boot with 
the below patch applied, and was wondering if you're aware of any 
problems in this area.  I'll probably post something more detailed 
tomorrow after trying a few things.

		-ben
-- 
"Time is what keeps everything from happening all at once." -- John Wheeler


diff -purN v2.6.12-rc4/include/linux/blkdev.h test-rc4/include/linux/blkdev.h
--- v2.6.12-rc4/include/linux/blkdev.h	2005-04-28 11:02:01.000000000 -0400
+++ test-rc4/include/linux/blkdev.h	2005-05-11 17:06:10.000000000 -0400
@@ -667,8 +667,8 @@ extern long blk_congestion_wait(int rw, 
 extern void blk_rq_bio_prep(request_queue_t *, struct request *, struct bio *);
 extern int blkdev_issue_flush(struct block_device *, sector_t *);
 
-#define MAX_PHYS_SEGMENTS 128
-#define MAX_HW_SEGMENTS 128
+#define MAX_PHYS_SEGMENTS 32
+#define MAX_HW_SEGMENTS 32
 #define MAX_SECTORS 255
 
 #define MAX_SEGMENT_SIZE	65536

             reply	other threads:[~2005-05-11 21:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-11 21:47 Benjamin LaHaise [this message]
2005-05-12  6:37 ` reducing max segments expected to work? Jens Axboe
2005-05-12 15:19   ` Benjamin LaHaise

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=20050511214749.GA14072@kvack.org \
    --to=bcrl@kvack.org \
    --cc=axboe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.