From: Spelic <spelic@shiftmail.org>
To: device-mapper development <dm-devel@redhat.com>
Subject: Source that sets max_segments
Date: Sat, 09 Feb 2013 03:09:41 +0100 [thread overview]
Message-ID: <5115AFE5.7030605@shiftmail.org> (raw)
Hello list
sorry this is a bit OT but I didn't know where to ask.
I am trying to raise max_segments above 128 by kernel recompile but it
seems I am not able to.
I have identified this place in the sources
void blk_set_default_limits(struct queue_limits *lim)
{
lim->max_segments = BLK_MAX_SEGMENTS;
....
so I have raised the value of corresponding enum BLK_MAX_SEGMENTS (which
was indeed set at 128), but I was surprised to notice that after booting
the new kernel the value is still stuck at 128, for all devices: sd*,
md*, dm-* .
So such value must come from elsewhere, but where?
( I am on 3.4.x fwiw.... )
Thanks in advance
reply other threads:[~2013-02-09 2:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5115AFE5.7030605@shiftmail.org \
--to=spelic@shiftmail.org \
--cc=dm-devel@redhat.com \
/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.