From: Simon Kirby <sim@netnation.com>
To: Jens Axboe <axboe@suse.de>
Cc: bartscgr@studbox.uni-stuttgart.de, linux-kernel@vger.kernel.org
Subject: Re: DVD_LU_SEND_AGID slow since 2.4.10
Date: Sun, 18 Nov 2001 02:51:02 -0800 [thread overview]
Message-ID: <20011118025102.A7651@netnation.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0111080054480.26201-100000@goofy.disney.gb> <20011108014151.A27093@suse.de>
In-Reply-To: <20011108014151.A27093@suse.de>
On Thu, Nov 08, 2001 at 01:41:51AM +0100, Jens Axboe wrote:
> > ever since 2.4.10 the SEND_AGID DVD_AUTH control seems to be very slow
> > (used in libdvdcss, freezes xine for up to 30sec). The code that's
> > executed seems to be:
> >
> > dvd_authinfo auth_info;
> >
> > memset( &auth_info, 0, sizeof( auth_info ) );
> > auth_info.type = DVD_LU_SEND_AGID;
> > auth_info.lsa.agid = *pi_agid;
> >
> > i_ret = ioctl( i_fd, DVD_AUTH, &auth_info );
> >
> > anybody here have any idea what might cause this? could this really be
> > just a caching problem caused by the new vm or is this something
> > completely different I observe here? The -ac kernel series doesn't seem to
> > have this problem on the same machine.
> >
> > Any comments apreciated, please cc as I'm not subscribed to the list
>
> Seems to have infested other (cdrom) ioctls as well. I'll take a look.
Any conclusion? It's quite annoying. It now takes around 30 seconds
before xine can even start playing a DVD.
Thinking it was the block device changes, I tried holding open /dev/hdd
and /dev/scd0, but it doesn't seem to make any difference.
Simon-
[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ sim@stormix.com ][ sim@netnation.com ]
[ Opinions expressed are not necessarily those of my employers. ]
prev parent reply other threads:[~2001-11-18 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 23:58 DVD_LU_SEND_AGID slow since 2.4.10 Guenter Bartsch
2001-11-08 0:41 ` Jens Axboe
2001-11-18 10:51 ` Simon Kirby [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011118025102.A7651@netnation.com \
--to=sim@netnation.com \
--cc=axboe@suse.de \
--cc=bartscgr@studbox.uni-stuttgart.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.