Thread (11 messages) 11 messages, 5 authors, 2017-02-08
  • (off-list ancestor, not in this archive)
  • memfill · Matthew Wilcox <willy@infradead.org> · 2017-02-06
  • Re: memfill · zhouxianrong <hidden> · 2017-02-07
  • Re: memfill · Minchan Kim <minchan@kernel.org> · 2017-02-07
  • Re: memfill · David Howells <dhowells@redhat.com> · 2017-02-07
  • Re: memfill · Matthew Wilcox <willy@infradead.org> · 2017-02-07
  • Re: memfill · David Howells <dhowells@redhat.com> · 2017-02-07
  • Re: memfill · Matthew Wilcox <willy@infradead.org> · 2017-02-07
  • Re: memfill · James Bottomley <James.Bottomley@HansenPartnership.com> · 2017-02-07
  • Re: memfill · Matthew Wilcox <willy@infradead.org> · 2017-02-08
  • Re: memfill · James Bottomley <James.Bottomley@HansenPartnership.com> · 2017-02-08
  • Re: memfill · Matthew Wilcox <willy@infradead.org> · 2017-02-08

Re: memfill

From: David Howells <dhowells@redhat.com>
Date: 2017-02-07 17:30:13
Also in: lkml

Matthew Wilcox [off-list ref] wrote:
You've misunderstood the purpose of memfill.  memfill allows the caller
to specify a pattern which is not a single byte in size, eg memfill(addr,
0x12345678, 64) would result in 0x12345678 being reproduced 16 times.
memset(addr, 0x12345678, 64) would result in 0x78 being reproduced
64 times.
Ah.  Should it take a unsigned int rather than an unsigned long?

David
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help