jo...@britannica.bec.de (Joerg Sonnenberger) writes:
For FFS2 it doesn't matter ATM, because
it is broken in that regard anyway, I think.
Fix it...
--
--
Michael van Elst
Internet: mlel...@serpens.de
A potential Snark may lurk in
On Fri, Jan 22, 2010 at 07:38:14AM +, Michael van Elst wrote:
Like most things, there is no universal correct answer here, simply
deciding always use bytes because it seems simpler is unlikely to be
the overall best answer.
I think the suggestion is to use block numbers (or some
On Fri, Jan 22, 2010 at 08:07:03AM +0100, Michael van Elst wrote:
On Fri, Jan 22, 2010 at 05:46:31AM +, David Holland wrote:
On Thu, Jan 21, 2010 at 10:30:20PM +, Michael van Elst wrote:
IMHO there need to be three different ways to specify block
offsets and block counts:
disk devices are accessed in units of 'blocks', a block can be
any size, however NetBSD makes assumptions in many places that
a block is 512 bytes or DEV_BSIZE bytes which makes it impossible
to use devices with different block sizes.
IMHO there need to be three different ways to specify
Hi! Iain,
First of all, I changed as follows.
In case cmd_pkt---
static void
btuart_dtl_output_cmd(device_t self, struct mbuf *m)
{
:
m_adj(m, sizeof(uint8_t)); /* remove hci_cmd_hdr_t's type */
M_PREPEND(m, sizeof(struct btuart_dtl_header), M_WAITOK);
dtlh =
what is the purpose of this change?
struct lwp is approx 700-1000 bytes on our platforms.
that's a significant chunk to remove from kernel stacks isn't it?
.mrg.
