From: Stas Sergeev <stssppnn@yahoo.com>
To: "Benjamin LaHaise" <bcrl@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Larger IO bitmap?
Date: Sun, 03 Nov 2002 02:56:51 +0300 [thread overview]
Message-ID: <3DC46643.5060909@yahoo.com> (raw)
Hello.
Benjamin LaHaise wrote:
>> you are using megabytes for your TSS's only !
> Keep in mind that a task's io bitmap is now lazily allocated, so by
> default no memory will be allocated for it.
Thanks, indeed browsing the 2.5 sources
at BK I see it is already done that way.
Had to upgrade before asking, as it doesn't
seem to be the case for 2.4(.19).
But then what are the reasons for the IO
bitmap to still be small at all? Are there
any reasons left?
> A similar enhancement
> for large vs small io bitmaps could be made by allowing the task io
> bitmap to be a variable size.
But is it really important?
next reply other threads:[~2002-11-02 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 23:56 Stas Sergeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-02 22:47 Larger IO bitmap? Stas Sergeev
2002-11-02 18:21 Stas Sergeev
2002-11-02 21:48 ` Jos Hulzink
2002-11-02 23:19 ` Benjamin LaHaise
2002-11-03 1:42 ` Denis Vlasenko
2002-11-02 23:38 ` Denis Vlasenko
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=3DC46643.5060909@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=bcrl@redhat.com \
--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