All of lore.kernel.org
 help / color / mirror / Atom feed
From: tingwei liu <tingw.liu@gmail.com>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How many params can be accept by kernel module at most?
Date: Mon, 1 Nov 2010 17:54:52 +0800	[thread overview]
Message-ID: <AANLkTin1_BqwPvxMQPxgEVpz6sdL13ecu0DDcDW009SM@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikkh+Pif7DuP3p-fH2=5_otX7N0NSjSB2h13yFC@mail.gmail.com>

My description is correct or not ?

2010/11/1 tingwei liu <tingw.liu@gmail.com>:
> The params are transferred by command line. And the params are all in
> program statically. So the stack size determine the params number. For
> example: stack size is 4K,and params are unsigned int type with 4
> bytes,so the max number of params is 1 thousand。
>
> 2010/11/1 tingwei liu <tingw.liu@gmail.com>:
>> What's the meaning of dynamically and statically?
>> You response help me much. Thank you
>>
>> 2010/11/1 Américo Wang <xiyou.wangcong@gmail.com>:
>>> On Mon, Nov 01, 2010 at 02:17:23PM +0800, tingwei liu wrote:
>>>>How many params can be accept by kernel module at most?
>>>
>>> If you mean dynamically, these parameters are passed as a whole to kernel,
>>> from the source code, you can see the max length is ~0UL>>1.
>>>
>>> If you mean statically, IOW, the max paramenters you can provide in your module,
>>> this is limited by ELF section size.
>>>
>>> Hope this helps.
>>>
>>
>

  reply	other threads:[~2010-11-01  9:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01  6:17 How many params can be accept by kernel module at most? tingwei liu
2010-11-01  9:29 ` Américo Wang
2010-11-01  9:32   ` tingwei liu
2010-11-01  9:49     ` tingwei liu
2010-11-01  9:54       ` tingwei liu [this message]
2010-11-01  9:59       ` Américo Wang
2010-11-01 13:42         ` tingwei liu
2010-11-02  1:40           ` Thiago Farina

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=AANLkTin1_BqwPvxMQPxgEVpz6sdL13ecu0DDcDW009SM@mail.gmail.com \
    --to=tingw.liu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.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.