From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Cameron, Steve" <Steve.Cameron@hp.com>
Cc: linux-kernel@vger.kernel.org, arrays@hp.com
Subject: Re: [PATCH] reduce stack in cpqarray.c::ida_ioctl()
Date: Thu, 3 Apr 2003 13:21:37 +0000 [thread overview]
Message-ID: <20030403132137.746cf532.rddunlap@osdl.org> (raw)
In-Reply-To: <45B36A38D959B44CB032DA427A6E10640451339C@cceexc18.americas.cpqcorp.net>
On Thu, 3 Apr 2003 14:18:57 -0600 "Cameron, Steve" <Steve.Cameron@hp.com> wrote:
|
| > This patch to 2.5.66 reduces stack usage in ida_ioctl() by about
| > 0x500 bytes (on x86).
|
| Looks ok to me, (but i haven't tried it.)
Me either (-ENOHARDWARE).
| > There is a possibility that the allocation here should be done one time
| > only and the buffer pointer saved for re-use instead of allocating it
| > on each call to ida_ioctl. If that's desirable, I'll have a few
| > questions.
|
| No, I don't think so. I think we should
| allow for the possibllity of concurrent calls
| to this ioctl. (whether linux allows it is
| another question. I think it used to be the case
| that only one ioctl could get in at a time... I can't
| recall if it's still that way.)
Well, my questions were along those lines, like:
. allocate a buffer per hba or per disk?
. how much is ida_ioctl() [passthru] used?
. it's not on a normal(!?!) read path, is it?
if so, using kmalloc() that could fail would be a bad idea.
--
~Randy
next prev parent reply other threads:[~2003-04-03 21:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 20:18 Cameron, Steve
2003-04-03 13:21 ` Randy.Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-03 21:35 Cameron, Steve
2003-04-03 12:03 Randy.Dunlap
2003-04-04 0:30 ` Jörn Engel
2003-04-03 17:33 ` Randy.Dunlap
2003-04-04 7:56 ` Jörn Engel
2003-04-04 8:44 ` Randy.Dunlap
2003-04-04 16:54 ` Jörn Engel
2003-04-04 8:09 ` Jens Axboe
2003-04-04 9:51 ` Jörn Engel
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=20030403132137.746cf532.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=Steve.Cameron@hp.com \
--cc=arrays@hp.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
all inboxes | Powered by JetHome®