Re: clarifying the construction of read-only /proc files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  as a short followup to that earlier post, the value of seq files is
obviously to break down the possible output of *lots* of data into
bite-sized pieces.  but how large can those pieces be?

  from fs/seq_file.c, in the routine traverse():

       if (!m->buf) {
                m->buf = kmalloc(m->size = PAGE_SIZE, GFP_KERNEL);
                if (!m->buf)
                        return -ENOMEM;

that suggests to me that a single, machine-specific PAGE_SIZE is the
hard limit on a single seq_file data transfer.  is that correct?

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

        Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com:          http://cli.gs/WG6WYX
========================================================================

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux