mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Rolf Eike Beer" <eike-kernel@sf-tec.de>
Cc: "Greg KH" <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: Exporting array data in sysfs
Date: Mon, 18 Sep 2006 11:41:06 -0400	[thread overview]
Message-ID: <d120d5000609180841v436f7a32l78b26fc72f48f92a@mail.gmail.com> (raw)
In-Reply-To: <200609181718.35491.eike-kernel@sf-tec.de>

On 9/18/06, Rolf Eike Beer <eike-kernel@sf-tec.de> wrote:
> Dmitry Torokhov wrote:
> > On 9/18/06, Rolf Eike Beer <eike-kernel@sf-tec.de> wrote:
> >>Dmitry Torokhov wrote:
>
> >>> http://www.ussg.iu.edu/hypermail/linux/kernel/0503.2/1155.html
>
> >> The limitation to 999 entries should go.
> >
> > It is not really a limitation but rather a safeguard. Do you really
> > expect to have arrays with that many attributes?
>
> At least I don't know how much they will be. If the user wants to do crazy
> things... :) I'm currently hacking on a store_n implementation, perhaps I'll
> be able to show some code tomorrow.
>

I do not think you shoudl allow user do crazy things. The memory is
kmalloced so there naturally a limit on number of attrinutes that can
be created. And I am not sure abot usefulness of resizing form
usespace.
Could you give me an example of a user who needs dynamic attribute arrays?

-- 
Dmitry

  reply	other threads:[~2006-09-18 15:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-18 11:59 Rolf Eike Beer
2006-09-18 12:44 ` Greg KH
2006-09-18 13:41   ` Rolf Eike Beer
2006-09-18 13:56     ` Dmitry Torokhov
2006-09-18 14:22       ` Rolf Eike Beer
2006-09-18 14:59         ` Dmitry Torokhov
2006-09-18 15:18           ` Rolf Eike Beer
2006-09-18 15:41             ` Dmitry Torokhov [this message]
2006-09-18 15:57               ` Rolf Eike Beer

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=d120d5000609180841v436f7a32l78b26fc72f48f92a@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=eike-kernel@sf-tec.de \
    --cc=greg@kroah.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®