On Thu, 2008-03-27 at 11:08 +0100, Holger Schurig wrote:
> > struct lbs_event {
>
> add "struct list_head list;"
>
> > u32 event; /* MACREG_INT_CODE_xxxxx */
> > u32 len;
> > u8 buf[LBS_UPLD_SIZE];
> > };
>
> Hmm, buf is LBS_UPLD_SIZE (2312 bytes). However, if_cs.c,
> if_sdio.c and if_usb.c use LBS_CMD_BUFFER_SIZE, which is 2048.
>
>
> > void lbs_interrupt(struct lbs_private *priv, u32 event, u8
> > *resp_data, u32 resp_len) {
>
> With this approach, the driver would have copy the date from the
> hardware into local buffer. Then it would call lbs_interrupt()
> with a pointer to this local buffer. Then lbs_interrupt() would
> memcpy() this. Then something in main.c and/or cmd.c would again
> memcpy() this.
The USB and SDIO driver have skbs that they currently just memcpy to
priv->upld_buf, in this case lbs_interrupt() would take over that
responsibility, so you'd still have the same # of copies: 1.
It looks like the CF driver uses priv->upld_buf directly, which it can
do because it's holding the spinlock, because it's trying to do so much
work from hw_get_int_status(), which is something it shouldn't be doing.
I'd argue that the CF driver should also have an internal buffer like
the SDIO and USB drivers do, and then there's still only one copy.
The problem with using upld_buf (and therefore zero-copy in the CF
driver) is that you have no idea how long a read from the card will
really take, and what errors might happen during the read from the card.
And you're holding the spinlock with interrupts disabled while you're
doing that. That read from the card is going to take a lot more time
than a simple memcpy in lbs_interrupt(), and you want to minimize the
time you're holding the spinlock anyway. That's the reason the CF
driver has this problem in the first place, because it's trying to do
too much under the spinlock.
Dan
> Let's split lbs_interrupt() into two functions:
>
> struct lbs_event *lbs_get_free_event(struct lbs_private *priv);
>
> void lbs_handle_event(struct lbs_private *priv, struct lbs_event
> *event);
>
> Then the hardware driver can do:
>
> struct lbs_event *event = lbs_get_free_event(priv);
> if (!event)
> ...
> if_cs_receive_cmdres(priv, &event->buf, &event->len);
> lbs_handle_event(priv, event);
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
