I am now semi retired. So I have a bit more time to volunteer. How can I help the cause, please? I am a native English speaker and a teacher. I used to be a software engineer. I have worked in libraries and have a bit of training in library science.
Respectfully, Elise Scher KI6PUO On Wed, Mar 27, 2024 at 9:03 AM <[email protected]> wrote: > Send Pgubook-readers mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.nongnu.org/mailman/listinfo/pgubook-readers > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Pgubook-readers digest..." > > > Today's Topics: > > 1. Re: About Buffer Size Restriction (Jonathan Bartlett) > 2. Re: About Buffer Size Restriction (Kenan Kartal) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 26 Mar 2024 15:47:55 -0500 > From: Jonathan Bartlett <[email protected]> > To: Kenan Kartal <[email protected]> > Cc: [email protected] > Subject: Re: About Buffer Size Restriction > Message-ID: > < > cahrtq6ribmw9zw4t_r6b9twseuvv_jswjtlsmmylbul3csk...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Kenan - > > Thanks for reaching out. > > It's been a while since I wrote this, but, I think it was partially based > on SSIZE_MAX and partially based on other write operation limits on the > kernel. Most write operation limits have been increased since then, but, > among the various things, sockets, files, etc., keeping the write size low > helps keep you from being on the wrong side of an unpredictable situation. > > Jon > > > On Tue, Mar 26, 2024 at 7:57 AM Kenan Kartal <[email protected]> > wrote: > > > Hello, > > > > In Chapter 5. Dealing with Files - Using Files in a Program; the buffer > > size in the bss section is suggested to never exceed 16000 for various > > reasons. What might those reasons be? > > > > I like the reading so far. I am writing it for x86_64; so, I presume > > this restriction doesn't apply. Only thing I have found on my machine > > (Linux + GNU on x86_64) is that `read` accepts `SSIZE_MAX` which is > > `INT_MAX`. However, I would still appreciate the reasoning for the > > original restriction. > > > > Sincerely, > > > > -- > > Kenan Kartal > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://lists.nongnu.org/archive/html/pgubook-readers/attachments/20240326/81149dc6/attachment.htm > > > > ------------------------------ > > Message: 2 > Date: Wed, 27 Mar 2024 07:53:37 +0300 > From: Kenan Kartal <[email protected]> > To: Jonathan Bartlett <[email protected]> > Cc: [email protected] > Subject: Re: About Buffer Size Restriction > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > Thanks Mr. Bartlett, > > It is good to have these knowledge under the belt in case we need to > work with older hardware. > > Regards, > > On 26.03.2024 23:47, Jonathan Bartlett wrote: > > Kenan - > > > > Thanks for reaching out. > > > > It's been a while since I wrote this, but, I think it was partially based > > on SSIZE_MAX and partially based on other write operation limits on the > > kernel. Most write operation limits have been increased since then, but, > > among the various things, sockets, files, etc., keeping the write size > low > > helps keep you from being on the wrong side of an unpredictable > situation. > > > > Jon > > > > > > On Tue, Mar 26, 2024 at 7:57 AM Kenan Kartal <[email protected]> > > wrote: > > > >> Hello, > >> > >> In Chapter 5. Dealing with Files - Using Files in a Program; the buffer > >> size in the bss section is suggested to never exceed 16000 for various > >> reasons. What might those reasons be? > >> > >> I like the reading so far. I am writing it for x86_64; so, I presume > >> this restriction doesn't apply. Only thing I have found on my machine > >> (Linux + GNU on x86_64) is that `read` accepts `SSIZE_MAX` which is > >> `INT_MAX`. However, I would still appreciate the reasoning for the > >> original restriction. > >> > >> Sincerely, > >> > >> -- > >> Kenan Kartal > >> > >> > > > > -- > Kenan Kartal > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Pgubook-readers mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/pgubook-readers > > > ------------------------------ > > End of Pgubook-readers Digest, Vol 70, Issue 2 > ********************************************** >
