From: Celelibi <celelibi@gmail.com>
To: linux-newbie <linux-newbie@vger.kernel.org>,
linux-c-programming@vger.kernel.org
Subject: Re: cat a /proc entry
Date: Wed, 21 Nov 2012 15:36:57 +0200 [thread overview]
Message-ID: <CAJR2zJ-dOT3YbzHC55+Z-t98YqGaX=dEm9uY6mqxK6G1QXpKtg@mail.gmail.com> (raw)
In-Reply-To: <CAGZFCEFaWrXMDAjCrXipiPyLxeWaQzGgn=GtLZhFHDwdrMAHcw@mail.gmail.com>
2012/11/21, ratheesh kannoth <ratheesh.ksz@gmail.com>:
> Hi,
>
> is there size limit on the buffer content as i am using "cat" command
> ( so ,not allocating any buffer in userspace, so not doing any
> copy_to_user from kernel; simply doing sprintf(buffer, %s , data )
> from kernel for a big data )
>
> -Ratheesh
Hello,
I'm not sure to understand your problem.
Do you write userland or kernelland code?
If you write kernel code, why don't you just use the API behind the
/proc file system?
If you write userland code, what is your problem with the buffer
allocation? You can allocate a buffer as big as your memroy allows it.
Celelibi
prev parent reply other threads:[~2012-11-21 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 4:04 cat a /proc entry ratheesh kannoth
2012-11-21 13:36 ` Celelibi [this message]
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='CAJR2zJ-dOT3YbzHC55+Z-t98YqGaX=dEm9uY6mqxK6G1QXpKtg@mail.gmail.com' \
--to=celelibi@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=linux-newbie@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).