On 7/24/07, Andrew Morton <[email protected]> wrote: > On Tue, 24 Jul 2007 16:12:56 -0400 Robin Getz wrote: > > On Tue 24 Jul 2007 14:12, Andrew Morton pondered: > > > Oh well, it sounds like we need the super-duper fast version. Keep it > > > as simple as possible, please. > > > > What about: > > > > int log_buf_copy(void *dest, int idx, size_t n); > > > > starting at index idx - copy n bytes to dest, return the number of bytes > > copied (in case there are not n bytes in the log_buf yet). > > Sounds sensible. I'd make it return size_t and take a char* arg though. > Or just use `int' - size_t is a bit of a pain and this is all kernel-internal > anwyay. attached -mike
Attachment:
linux-log_buf_read.patch
Description: Binary data
- Follow-Ups:
- Re: early_printk accessing __log_buf
- From: Andrew Morton <[email protected]>
- Re: early_printk accessing __log_buf
- From: Bryan Wu <[email protected]>
- Re: early_printk accessing __log_buf
- References:
- early_printk accessing __log_buf
- From: Robin Getz <[email protected]>
- Re: early_printk accessing __log_buf
- From: Robin Getz <[email protected]>
- Re: early_printk accessing __log_buf
- From: Andrew Morton <[email protected]>
- Re: early_printk accessing __log_buf
- From: Robin Getz <[email protected]>
- Re: early_printk accessing __log_buf
- From: Andrew Morton <[email protected]>
- early_printk accessing __log_buf
- Prev by Date: Re: [RFC 12/26] ext2 white-out support
- Next by Date: Re: commit 80917728e43e248155c019f743655806b582b099
- Previous by thread: Re: early_printk accessing __log_buf
- Next by thread: Re: early_printk accessing __log_buf
- Index(es):