From: Jean-Eric Cuendet <jean-eric.cuendet@linkvest.com>
To: mingming cao <cmm@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Rework of /proc/stat
Date: Thu, 07 Mar 2002 12:16:16 +0100 [thread overview]
Message-ID: <3C874C00.8080309@linkvest.com> (raw)
In-Reply-To: <3C86553E.3070608@linkvest.com> <E16ik6y-0008Qf-00@the-village.bc.nu> <3C86BEB0.4090203@us.ibm.com>
> Basically, statistic data are moved from the global kstat structure to
> the request_queue structures, and it is allocated/freed when the
> request queue is initialized and freed. This way it is
>
Why do you dynamically allocate the stat structure? Wouldn't it be
better static in the request struct?
You don't win anything with that since is you create the queue, it's to
be accessed, so the struct will be allocated ASAP.
No?
--
Jean-Eric Cuendet
Linkvest SA
Av des Baumettes 19, 1020 Renens Switzerland
Tel +41 21 632 9043 Fax +41 21 632 9090
E-mail: jean-eric.cuendet@linkvest.com
http://www.linkvest.com
--------------------------------------------------------
next prev parent reply other threads:[~2002-03-07 11:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 17:43 [PATCH] Rework of /proc/stat Jean-Eric Cuendet
2002-03-06 20:08 ` James Stevenson
2002-03-06 22:42 ` Alan Cox
2002-03-07 1:13 ` mingming cao
2002-03-07 11:16 ` Jean-Eric Cuendet [this message]
2002-03-07 11:48 ` Christoph Hellwig
2002-03-07 13:50 ` Alan Cox
2002-03-07 13:53 ` Jean-Eric Cuendet
2002-03-07 14:17 ` Alan Cox
2002-03-07 11:11 ` Jean-Eric Cuendet
2002-03-07 11:48 ` Arjan van de Ven
2002-03-07 12:48 ` Alan Cox
2002-03-07 11:40 ` Jean-Eric Cuendet
2002-03-07 12:51 ` Alan Cox
[not found] <E16lBe4-0006ly-00@the-village.bc.nu>
2002-03-13 16:41 ` Jean-Eric Cuendet
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 17:16 Jean-Eric Cuendet
2002-03-06 17:25 ` Russell King
2002-03-06 19:48 ` Dominik Kubla
2002-03-07 11:12 ` Jean-Eric Cuendet
2002-03-07 1:07 ` mingming cao
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=3C874C00.8080309@linkvest.com \
--to=jean-eric.cuendet@linkvest.com \
--cc=cmm@us.ibm.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